-
Notifications
You must be signed in to change notification settings - Fork 5
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
[🐛 Bug]: User provided secret key is not used when tests are running #40
Comments
Greetings, I am currently trying to use the synpress pkg to build and execute e2e tests on an dapp deployed in Agoric, more specifically KREAd. There are some questions related to this issue that I would like to clarify:
Thank you in advance. |
@Jorge-Lopes, currently, there's a known issue where the tests default to using the mnemonic To add your preferred mnemonic for testing, you can provide it as a parameter to the setupWallet function. For example: cy.setupWallet({
secretWords:
'orbit bench unit task food shock brand bracket domain regular warfare company announce wheel grape trust sphere boy doctor half guard ritual three ecology'
}). |
@rabi-siddique Thank you very much for your suggestion. |
🔎 Have you searched existing issues to avoid duplicates?
🧪 Have you tested your code using latest version of Synpress?
💡 Are you able to provide enough information to be able to reproduce your issue locally?
Synpress version
3.8.1
Node.js version
18.18.0
Operating system
Linux Mint
Run mode
Playwright + Synpress (as plugin)
CI platform (if applicable)
No response
Are you running your tests inside docker? (if applicable)
What happened?
I tried again with the right mnemonic:
When the users add a
SECRET_WORDS
env variable, the address shown in the tests isagoric1p2aqakv3ulz4qfy2nut86j9gx0dx0yw09h96md
. It does not correspond to the mnemonic provided by the user.What is your expected behavior?
No response
How to reproduce the bug.
Add a
SECRET_WORDS
env variable. You will notice that in tests, the valueSECRET_WORDS
is not being used.Relevant log output
No response
The text was updated successfully, but these errors were encountered: