test: add non-debian based test for gawk

intel / cve-bin-tool

The CVE Binary Tool helps you determine if your system includes known vulnerabilities. You can scan binaries for over 200 common, vulnerable components (openssl, libpng, libxml2, expat and others), or if you know the components used, you can get a list of known vulnerabilities associated with an SBOM or a list of components and versions.

GNU General Public License v3.0

1.21k stars 460 forks source link

Related: #3395

I just merged #3395 (a gawk checker) and it currently only has a debian-based file test. We try when possible to have tests against multiple linux distributions so that we can tell patterns aren't specific to only one form of packaging, so it would be good to add a second file based test here.

Useful links for writing the test:

Instructions on how to find files for checkers are part of the checker documentation: https://github.com/intel/cve-bin-tool/blob/main/cve_bin_tool/checkers/README.md
How to find a good binary file to use for tests
How to add a test against a real file
You may also want to know how to run a single test using pytest so that you can run just the tests you wrote and not the whole test suite.

It's also possible that the recently merged checker won't work against anything but debian. If that's the case, please open a PR to add a note in the checker file itself saying something like "At this time, this checker works only against debian-based packages".

Short tips for new contributors:

cve-bin-tool's contributor docs
If you've contributed to open source but not this project, you might just want our checklist for a great pull request
cve-bin-tool uses https://www.conventionalcommits.org/ style for commit messages, and we have a test that checks the title of your pull request (PR). A good potential title for this one is in the title of this issue.
You can make an issue auto close by including a comment "fixes #ISSUENUMBER" in your PR comments where ISSUENUMBER is the actual number of the issue. This "links" the issue to the pull request.

Claiming issues:

You do not need to have an issue assigned to you before you work on it. To "claim" an issue either make a linked pull request or comment on the issue saying you'll be working on it.
If someone else has already commented or opened a pull request, assume it is claimed and find another issue to work on.
If it's been more than 1 week without progress, you can ask in a comment if the claimant is still working on it before claiming it yourself (give them at least 3 days to respond before assuming they have moved on).

intel / cve-bin-tool

test: add non-debian based test for gawk #3409