Skills Assignment SA3-PT: Model Basics Practice Test

Getting Started

1. Access the GitHub organization’s repositories page.
   • In your web browser, log into GitHub.
   • Navigate to the repositories page of the memphis-comp-7012-2024-08fall GitHub organization.
2. Create a new repository from the template.
   • Click the New repository button at the top-right of the page.
   • Fill out the Create a new repository form as follows:
     • Repository template: Select template-sa3-pt.
     • Owner: Select memphis-comp-7012-2024-08fall.
     • Repository name: Use the form below to generate the name for your repository.
       • It is required that your repository’s name precisely follow the format produced by the form.
     • Select Private, so that only you and your instructors can access your repository.
   • Once you have filled out all the fields, click the Create repository button at the bottom right of the page.
3. Clone the repository and set up your local environment.
   • In your terminal, clone the newly created repository into your workspace folder.
   • Set up local repository by following steps similar to those in the Running Apps demo.

Your UofM Username Submission Opportunity 1 2 3

sa3-pt-hjsimpson-1

Task

You must implement a Rails model class (including migration) as per this class diagram:

You must seed the database (using the seeds.rb script) with the following Book records:

Title	Author	Year	Publisher
Jaws	Peter Benchley	1974	Doubleday
Murder on the Orient Express	Agatha Christie	1934	Collins Crime Club
Slaughterhouse-Five	Kurt Vonnegut	1969	Delacorte
Fahrenheit 451	Ray Bradbury	1953	Ballantine Books
Death on the Nile	Agatha Christie	1937	Collins Crime Club

You must create an index page that displays all the Book records stored in the database, like this:

Each “Show” link on the index page must link to a show page for the record, and the show pages must look like this:

Detailed Specifications

• Feature: Browse Books
  • User Story:
    • As a visitor,
    • I want to see a list of available books
    • So that I can choose one to learn more about
  • Scenario: Viewing the book index page content
    • Given I have created two sample Book records
    • And I am on the /books page
    • Then I should see an h1 element with text “Book List”
    • And I should see a table with a header row with headers “Title”, “Author”, and an empty header
    • And I should see two table body rows with the sample records’ title, author, and a link with text Show.
  • Scenario: Redirecting from the root page to the books page
    • When I visit the root URL
    • Then I should be automatically redirected to the /books page
• Feature: View Book Details
  • User Story:
    • As a visitor,
    • I want to see detailed information about a selected book
    • So that I can learn more about it
  • Scenario: Viewing a book show page content
    • Given I have created a sample Book record
    • And I am on its /books/:id page
    • Then I should see an h1 element with the book title
    • And I should see a list of book attributes in a ul element containing exactly 3 li items
    • And I should see an li item with the text “Author: [Author’s Name]”
    • And I should see an li item with the text “Year Published: [Year]”
    • And I should see an li item with the text “Publisher: [Publisher’s Name]”
    • And I should see a link with text “Back to Book List”
  • Scenario: Navigating to a book show page from the index page
    • Given I have created a sample Book record
    • And I am on the /books page
    • When I click on a book’s “Show” link
    • Then I should be on the /books/:id page for the selected book
  • Scenario: Navigating back to the book index page from the show page
    • Given I have created a sample Book record
    • And I am on its /books/:id page
    • When I click on the “Back to Book List” link
    • Then I should be on the /books page

Additional Constraints:

• You must follow the standard Rails conventions:
  • Each page must have a path helper following the standard Rails convention:
    • /books is books_path
    • /books/:id is book_path
  • /books routes to BooksController#index
  • /books/:id routes to BooksController#show
• Links must use the link_to helper with the appropriate path helper
  • The scenario “Navigating back to the book index page from the show page” should use root_path
• Model class and attributes must be named as instructed
• 5 seeds must be created as instructed upon seeding
• All HTML tags must be properly closed
• No duplication of head/style/body elements in the rendered HTML

Note: Italicized requirements will be manually confirmed by the graders.

Testing Your Work with RSpec

Each of the feature stories above corresponds to an RSpec feature spec. These tests (and others for the additional constraints) have been provided in the repository to help you check whether your implementation meets the requirements.

Recommended Workflow

1. Read through the detailed specifications first. Understand what is required for each page and scenario.
2. Approach 1 - for those familiar with Test-Driven Development (TDD):
   • Run rspec spec/features to execute the feature tests.
   • Try to write the minimum amount of code needed to make each test pass.
   • Watch the tests fail and pass as you meet each requirement.
   • At the end, run all the provided tests with the rspec command to check if everything passes.
     • Note that not all tests are feature tests, so it is necessary to run rspec at the end to ensure that all tests are run.
3. Approach 2 - for those less experienced with testing:
   • Work through the specifications step by step, ensuring your implementation meets each requirement.
   • Once you’ve completed your implementation, run all the tests with the rspec command to check if everything passes.

Either of the above approaches is fine, as long as all tests pass by the end.

How to Submit Your Work

Once you’ve completed the task and confirmed that all tests pass:

1. Commit your changes:

   • Add all your changes:

     git add -A
     

   • Commit your work with a meaningful message:

     git commit -m "Completed SA3 Practice Test"
     

2. Push your changes to GitHub:

   • Push your commits to the remote repository:

     git push
     

3. Take Screenshots:
   • Open your Rails app in the browser and take two screenshots:
     • One of the Books index page (/books).
     • One of the Books show page for Fahrenheit 451 (/books/4).
   • Ensure that your desktop background or terminal prompt with your unique username is visible in the screenshot.
4. Submit to Canvas:
   • In Canvas, submit:
     • The two screenshots of your app running in the browser.
     • The link to your GitHub repository where your code is hosted.
   • You may submit all 3 in a single document.