feat(ci): add e2e tests to staging deployment workflow#1693
Merged
Conversation
983e5bc to
6601d80
Compare
9be1fdf to
3196c57
Compare
4b2a94c to
7e3d300
Compare
- Separate deploy-staging and e2e-tests into new deploy-staging.yaml workflow - Maintain dependency for e2e on deploy-staging
7e3d300 to
a01c137
Compare
b2bebe9 to
a01c137
Compare
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
Adds end-to-end (e2e) tests to the CI workflow that run automatically after staging deployment. This ensures staging is tested before considering it safe, while keeping production deployments non-blocking.
Changes
Testing
Disclaimer: There is a commit just to test the CI that remove guardrails, this will be removed before merge
Closes #1684