Draft: Fix Cypress in Docker Environment #403
Draft
Conversation
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
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.
🔥 Summary
Closes #378
After refactoring to Sidecar and splitting the mono repo up our Cypress tests haven't been running properly. In a few previous tickets we address fixing the E2E tests to run on our local machines. But we have yet to address Cypress in the docker environment. Which will be required if/when we want to have E2E tests in our CI.
This ticket addresses the broken Cypress state in docker
😤 Problem / Goals
🤓 Solution
🗒️ Additional Notes