EPIC: add pages e2e tests

[alishaevn]

story

add cypress tests to make sure that each page renders correctly

acceptance criteria

• <Home /> renders with the appropriate components
  • <Home /> renders in the loading state when applicable
  • <Home /> renders in the error state when applicable
• <Service /> renders with the appropriate components
  • <Service /> renders in the loading state when applicable
  • <Service /> renders in the error state when applicable
• <Requests /> renders with the appropriate components e2e test: requests user flow #192
  • <Requests /> renders in the loading state when applicable e2e test: requests user flow #192
  • <Requests /> renders in the error state when applicable e2e test: requests user flow #192
• <Request /> renders with the appropriate components e2e test: individual request page #218
  • <Request /> renders in the loading state when applicable e2e test: individual request page #218
  • <Request /> renders in the error state when applicable e2e test: individual request page #218
• <NewRequest /> renders with the appropriate components
  • <NewRequest /> renders in the loading state when applicable
  • <NewRequest /> renders in the error state when applicable
• <Browse /> renders with the appropriate components Refactor Browse Page tests & add for page #251
  • <Browse /> renders in the loading state when applicable Refactor Browse Page tests & add for page #251
  • <Browse /> renders in the error state when applicable Refactor Browse Page tests & add for page #251

resources

• https://nextjs.org/docs/testing#creating-your-tests

[summer-cook]

These tests are testing the full page, and the appropriate components render or not based on API calls. The way nextJS is set up, the api calls technically live outside of the component. In order to test pages properly, these need to be e2e tests (using stubbed responses) instead