-
Notifications
You must be signed in to change notification settings - Fork 96
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
automation test coverage addition #112
automation test coverage addition #112
Conversation
@pcheremu can you please review this PR? |
echo "---------------------------------" | ||
|
||
echo "> zksync-cli contract write" | ||
npx zksync-cli contract write --chain zksync-sepolia --contract 0xE6c391927f0B42d82229fd3CFe3426F209D16b48 --method "setGreeting(string _greeting) " --args "New Test ARG" --private-key 32e2e997e1a2d91cee03f77f903103ce6f50301e125307cc4bcaa87313f1a13e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we must not store --private-key in direct access even if it belongs to a testnet.
I will replace it to the test solution with a fix: testnet_private_key: process.env.E2E_TESTNET_PK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
process.env. --> means that it will be in git actions env. this is also not really secure but may be possible for a testnet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Of course make sense from security side.
8b85a29
to
72e8084
Compare
#123 - latest branch with your included tests. |
What 💻
In the scope of this PR next automation tests were added:
List of test cases automated:
Why ✋
Evidence 📷
Include screenshots, screen recordings, or
console
output here demonstrating that your changes work as intendedNotes 📝