-
Notifications
You must be signed in to change notification settings - Fork 9
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
chore(RHTAPWATCH-691): verify-rpms test to fail on unsigned RPMs #35
Conversation
76bd495
to
f69ca56
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.
I think the unclarity is coming from the fact that we're not testing here our ability to fail on unsigned RPMs. We're testing our ability to fail based on the output of the function that generates the output.
f69ca56
to
4eac2b2
Compare
4eac2b2
to
72a6ef5
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.
lgtm
The e2e test for the verify-rpms script checked only a scenario where it should not fail when unsigned RPMs or errors exists. Adds tests for multiple scenarios - where the script should and should not fail when encountering unsigned RPMs or other errors. This lead to a refactor which changed the failing responsability from which fails the process from "generate_output" to the main function. Signed-off-by: Omer <[email protected]>
72a6ef5
to
8871cf1
Compare
The e2e test for the verify-rpms script checked
only a scenario where it should not fail when unsigned RPMs
or errors exists.
Adds tests for multiple scenarios - where the script should
and should not fail when encountering unsigned RPMs or other errors.
This lead to a refactor which changed the failing responsability
from which fails the process from "generate_output" to the
main function.