-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Initial E2E test of chrome extensions #156
Merged
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
@jrwbabylonlab @totraev please review this PR, it should work with these versions:
so I can implement further PRs for things like #157 |
gbarkhatov
force-pushed
the
feat/e2e-initial
branch
from
January 5, 2025 08:36
e61f7ea
to
a0ca1da
Compare
Closed
jrwbabylonlab
approved these changes
Jan 10, 2025
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.
In this PR the initial Chrome Extensions E2E setup is established
crx
extensions are extracted into the appropriate directories.env.local
fileVideo: https://youtu.be/nySA7lSc1Jo
I created few more issues to cover the future steps so this PR is not bloated even more:
ID
: E2E: CRX hash pub key #157simulate
andsignTx
E2E: BBN StargateClient simulate and signTx #161data-testid
E2E: data-testid for better selectors #162Closes: #138