Skip to content
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

Conversation

olehbairak
Copy link

@olehbairak olehbairak commented Jan 11, 2024

What 💻

In the scope of this PR next automation tests were added:

  • added automation test for the scope of basic flow checks for zksync-cli

List of test cases automated:

  • Test #1869
  • Test #1718
  • Test #1874
  • Test #1875

Why ✋

  • increase test coverage to cover most of the test cases and reduce workload for checking each new version of the cli

Evidence 📷

Include screenshots, screen recordings, or console output here demonstrating that your changes work as intended

Notes 📝

  • Any notes/thoughts that the reviewers should know prior to reviewing the code?

@olehbairak olehbairak added the automation autotests \ QA tests label Jan 11, 2024
@olehbairak olehbairak requested a review from a team as a code owner January 11, 2024 12:02
@olehbairak olehbairak self-assigned this Jan 11, 2024
@olehbairak olehbairak changed the title New automation tests automation test coverage addition Jan 11, 2024
@olehbairak
Copy link
Author

@pcheremu can you please review this PR?
Thank you in advance!

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

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

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

Copy link
Author

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.

@pcheremu
Copy link

pcheremu commented Feb 8, 2024

#123 - latest branch with your included tests.

@pcheremu pcheremu closed this Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation autotests \ QA tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants