we're importing the waresFixture so that we can,
access the new request page as an unauthorized user.

- ref: #360

Co-authored-by: alisha evans <[email protected]>

update the spec to account for the "new request" flow as an authorized
and unauthorized user. left TODO's for dalton, adrian and jean to pick
up when they return to this work.

Co-authored-by: Alisha Evans <[email protected]>

the intercept command was not ever working. now, we are expecting to use
the real api calls instead of mocked ones. this is to ensure that our
critical paths of browsing and creating a request are always working,
even when the api is updated.

I also refactored part of the browse page specs into the home page spec,
since that's the flow it was actually testing. also edited the cypress
config to make it more dynamic, which will help with this code existing
in the various client codebases.

there may potentially be hundreds of services on a page. to avoid
a timeout, we will only choose from 10 services. this still ensures
that a variety of dynamic forms are tested

Co-authored-by: Dalton Mcauliffe <[email protected]>
Co-authored-by: Adrian Carranza <[email protected]>

…serv/webstore into 360-fix-e2e-specs

Co-authored-by: DaltonMcauliffe <[email protected]>
Co-authored-by: Adrian Carranza <[email protected]>

loading a full browse page can take a while. the beachside biotech provider has 585
services and we're loading them all at once. certain services also have more complex
dynamic forms, which could mean it takes longer for them to load. increasing the
timeout for both operations prevents a failure due to time, opposed to assertion.

alphabetize the env variables
add the secrets to the github workflow so they can be picked up by CI

currently, all cypress tests are failing in ci through github actions
with the error below.
```
Error: [next-auth][error][NO_SECRET]
https://next-auth.js.org/errors#no_secret Please define a `secret` in production. MissingSecret [MissingSecretError]: Please define a `secret` in production.
```

the value of `NEXTAUTH_SECRET` has been set in the staging and production
github environments however. running the job in debug mode shows that the
secret's value is returning as null.
```
```

this commit is an attempt to get the tests to pass in ci by specifying the environment to use for cypress tests. hopefully it'll pick up the secret.

attempt to get around new ci error:
```
[next-auth][warn][NEXTAUTH_URL]
https://next-auth.js.org/warnings#nextauth_url
```

intercepting the `useFilteredWares` hook to only request 10 services.
we're still hitting the actual api, but hopefully this will speed things
up, while still providing dynamic form variety.

attempt to get around long timeouts by waiting for an expected element
to be on the page before continuing

when running specs locally with "cypress open" (headed), they pass.
they fail locally when running "cypress run"(headless) for timeout issues.
ci also runs headless, and gets timeout issues. I'm updating the config
to run headed in ci in an attempt to get them to pass.

ref: cypress-io/github-action#403 (comment)

the change in 3479ce0 still erred. I created a new
script for the cypress workflow to call specifically.

ref: cypress-io/github-action#403 (comment)

also wait for more elements to appear on the page before running assertions