-
Notifications
You must be signed in to change notification settings - Fork 28
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(int tests): add "incorrect checksum" scenario #429
feat(int tests): add "incorrect checksum" scenario #429
Conversation
please change the jira name to: STONEBLD-1895 |
The test LGTM 👍 nit: The only thing I might suggest is to update the README header on the test repo branch to match the test name |
Done |
97e86b4
to
a155b84
Compare
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.
Left a final nitpick, but otherwise LGTM 👍
tests/integration/test_yarn.py
Outdated
pytest.param( | ||
utils.TestParameters( | ||
repo="https://github.com/cachito-testing/cachi2-yarn-berry.git", | ||
ref="dcb16b5931a89ac642be2dcf9886e148a905bea4", |
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.
nit: Consider updating this ref to the latest on that branch so that it links to the updated README
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.
🤦
STONEBLD-1895 Signed-off-by: Ben Alkov <[email protected]>
a155b84
to
383442a
Compare
test data (cachi2-yarn-berry, "incorrect-checksum" branch)
STONEBLD-1895
Signed-off-by: Ben Alkov [email protected]
Maintainers will complete the following section
Docs updated (if applicable)Docs links in the code are still valid (if docs were updated)Note: if the contribution is external (not from an organization member), the CI
pipeline will not run automatically. After verifying that the CI is safe to run:
/ok-to-test
(as is the standard for Pipelines as Code)