#193 Add build step for e2e tests #199
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
1 task
brunomenezes
force-pushed
the
feature/193-add-build-step-for-e2e-tests
branch
from
e1cc5ca
to
306485b
Compare
brunomenezes
approved these changes
Jun 28, 2024
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.
I created a new
e2eworkflow for the e2e tests. It runs on successful deployment and is triggered only if the deployment is for therollups-explorer-sepoliaenvironment. This way, we can use the produced vercel preview url as base url for the e2e tests.I had to use Protection Bypass for Automation from the vercel settings, otherwise the e2e tests were failing because they were hitting the vercel login page.