jordan-sullivan / rancid-tomatillos Goto Github PK

Details:
When the user is viewing a specific movie view, they can click the home button in the navbar to return to the main dashboard.

Acceptance Criteria:

• User sees navbar with home option listed
• User clicks on the home button and no longer sees movie view.
• User is routed back to dashboard

• Basic JSX/ Component structure
• make basic CSs to style page
• use sample data to test UX/UI
• [ ]

Create Wireframe for Main page and Movie View page

Details:
The user should be able to go back to their previous view (or the next view) using the forward and back arrows.

Acceptance Criteria:

• User can navigate from movie view back to card container view using back/forward button.
• User can navigate from card container view back to movie view using back/forward button button.

Details:
The user should be able to click on a specific movie poster image to view that movie's details on a separate page.

Acceptance Criteria:

• User sees new page displaying the selected movie's information (movie image, statistics, genres)
• User can no longer see other movies
• User sees a navbar with an option to navigate back to the home page.

Details:
The user sees a dashboard with movie posters, titles, and ratings listed. They can scroll through to see all available movies at a glance so that they can select one.

Acceptance Criteria:

• User sees all 40 movies including the poster, title, and rating on main page
• User can scroll through main page to view all movies
• Navbar displays webpage name

• Build out basic JSX/component framework
• Implement CSS flex box to style card
• Access props and display poster, title, and star rating on card

• Add file to project
• Import data to needed files

Testing
4:
Team has successfully achieved 90%+ test coverage of all components
All async functionality is stubbed and tested
Async tests cover happy & sad paths
All application views are tested
All user flows are tested
3:
All application views are tested
All user flows are tested
Happy path async functionality is stubbed and tested
2:
Most application views are testeed
A valid attempt is made at testing user flows; some flows may be missing or incomplete
Little or no attempt at async testing was made
1:
Many application views tests are missing/failing
Little or no attempt is made at testing user flows
Little or no attempt is made at async testing
There are obvious, large gaps in testing app functionality

• Build out basic JSX/component framework
• Implement CSS grid for display
• Add props so that movie data can be accessed and passed down to card

Details
The user can see the movie's unique ID showing in the webpage URL after they click a specific movie.

Acceptance Criteria

• User must see an ID populate when specific movie card is clicked.

• Create JSX/component framework
• Add app name/ logo and placeholder buttons
• Add Conditional rendering to Home button to bring user back to main page from Movie View
• Add basic display CSS

• Make sure that 500 error shows when there is an error
• Should we have error handling for 400 as well?

• Test to make sure functionality exists on app
• Research if this is built into react router.

Clean up budget, revenue, ratings, etc to be easier to read for user.

• Set up imports/exports
• Set up initial JSX/component framework
• Build render method to display card container and navbar
• Add basic display css

• use conditional rendering to show a single movie’s details.
• create method in App Component to display selected movie by ID in Movie View
• create event handler/invocation in Card Component

on refresh, ratings render to 0 in stats box.

• Install react router on app
• Import react router components
• Wrap app component in router
• Build out dynamic rendering using movie ID so that MovieView displays correct information
• Home button returns page to MovieView