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
Pin Grype db for tests #120 #119
Conversation
Signed-off-by: Keith Zantow <kzantow@gmail.com>
Signed-off-by: Keith Zantow <kzantow@gmail.com>
Signed-off-by: Keith Zantow <kzantow@gmail.com>
Signed-off-by: Keith Zantow <kzantow@gmail.com>
@luhring this had to expand scope just a bit... tests failed because it's not using a static Grype db (I need to figure out how to do this; will add a ticket). Regardless, I needed a way to see the differences and update snapshots. Because of how jest reporting works, it was impossible to figure out what was going on without reverting to the normal reporter (instead of |
Signed-off-by: Keith Zantow <kzantow@gmail.com>
Signed-off-by: Keith Zantow <kzantow@gmail.com>
Signed-off-by: Keith Zantow <kzantow@gmail.com>
Signed-off-by: Keith Zantow <kzantow@gmail.com>
Signed-off-by: Keith Zantow <kzantow@gmail.com>
Signed-off-by: Keith Zantow <kzantow@gmail.com>
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.
Looks good! 👍
Download and use a static Grype database for snapshot testing. This started out because I missed some documentation referencing
v2
release instead ofv3
and had failed tests, so went down a bit of a rabbit hole making the tests reproducible and easier to understand by reverting back to the normal Jest reporter and removing the mountains of Grype output dumped to the logs.