testing: use production environment for e2e tests#1139
Merged
Conversation
When using the development environment if a request fails the screen is blocked by a helpful debugging message. I believe the `login` request that happens in the background regularly fails since we updated passport in the platform api. The e2e tests rely on the main branch of api to test against which explains why we transition into status tests failing without merging a PR that had failing status tests. Bug: T428389
|
Deployment previews on netlify for branch
|
Contributor
|
Happy to see this working now 🙌 |
deer-wmde
approved these changes
Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using the development environment if a request fails the screen is blocked by a helpful debugging message.
I believe the
loginrequest that happens in the background regularly fails since we updated passport in the platform api. This then blocks clicking any other elements.The e2e tests rely on the main branch of api to test against which explains why we transition into status tests failing without merging a PR that had failing status tests.
This commit uses the production environment for running the end to end tests. It also adjusts the npm install step. It retains the development environment for installation and uses npm ci[1] rather than install to make this test more deterministic and use the exact versions of packages specified in the lock file.
Finally this commit also uses a plain docker compose --wait and removes the -d since wait already implies detached mode. [2]
[1] https://docs.npmjs.com/cli/v11/commands/npm-ci
[2] https://docs.docker.com/reference/cli/docker/compose/up/
Bug: T428389