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

Incorporate integration testing #38

Closed
wagoodman opened this issue Jun 29, 2020 · 1 comment · Fixed by #54
Closed

Incorporate integration testing #38

wagoodman opened this issue Jun 29, 2020 · 1 comment · Fixed by #54
Assignees
Milestone

Comments

@wagoodman
Copy link
Contributor

Introduce integration-level testing that tests:

  • imgbom to vulnscan integrations: the appropriate package catalog is obtained from an underlying image
  • vulnscan to vulnscan-db: the appropriate store can be obtained from a flat file
  • internal vulnscan matching: given a catalog and vulnerability db obtained from standard execution paths, verify select matching results (direct exact matches, indirect matches, cpe matching, various vulnerability input sources appear in the results, etc)
@wagoodman wagoodman added this to the v0.1.0 milestone Jun 29, 2020
@wagoodman wagoodman added the blocked Progress is being stopped by something label Jul 12, 2020
@wagoodman
Copy link
Contributor Author

blocking since we're splitting the vulnscan repo & https://github.com/anchore/vulnscan-db/issues/30 will change the interface format substantially enough to probably wait for these changes to drop first.

@wagoodman wagoodman added size:medium and removed size:large blocked Progress is being stopped by something labels Jul 13, 2020
@wagoodman wagoodman self-assigned this Jul 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant