EPIC: add user flow e2e tests

[alishaevn]

story

setup end to end tests, which emulate user behavior, with cypress.

acceptance criteria

the following behaviors are tested:

• Authentication
  • a user can sign in
  • a user can sign out
  • the header shows "Sign In" for an unauthenticated user
  • the header shows "Sign Out" for an authenticated user
• Navigation
  ** may rethink these and add a single e2e test that just navigates to every route?
  • a user can navigate to "/browse"
  • a user can navigate to "/requests"
• Browsing (which is only a "search" in the mvp) Refactor Browse Page tests & add for page #251
  • a user can search from the home page and be directed to "/browse" with the proper query e2e test: user can conduct a blank and queried search from home page #201
    • blank search
    • actual search
  • a user can conduct a search on "/browse" e2e test: a user can conduct a search on "/browse" #210
    • includes a blank search
    • actual search
• Viewing all requests e2e test: requests user flow #192
  • a signed in user sees their requests, if they have any
  • a signed in user sees the correct "no requests" response if they don't have any requests
  • a signed out user is unauthorized to see requests
• Viewing a single request e2e test: individual request page #218
  • a signed in user can view an individual request page
  • a signed in user can view related documents
  • a signed in user can send a message to the supplier
• Creating a new request note: this will be the only true e2e test that doesn't use mock data
  • a signed in user can create a new ware request (from the browse and home pages)
  • a signed in user can create a new blank request (from the requests page)

resources

• https://nextjs.org/docs/testing#cypress
• https://docs.cypress.io/guides/end-to-end-testing/writing-your-first-end-to-end-test
• https://docs.cypress.io/guides/core-concepts/writing-and-organizing-tests#Folder-structure

[alishaevn]

@summer-cook what do you think about the new acceptance criteria? separating the tests into their features, not their components.

[summer-cook]

@alishaevn sure, that works - I added some for featured services too, but maybe they should be unit tests? Although we want to check that they are linking to the correct request page, which then makes me think those should be e2e

[alishaevn]

@summer-cook

I added some for featured services too, but maybe they should be unit tests?

correct. testing whether they show on the page should be a unit test

we want to check that they are linking to the correct request page

this feature is documented in the first checkbox under "creating a new request"