-
Notifications
You must be signed in to change notification settings - Fork 18
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
add tests for advisory parsing #100
Comments
I can give this a try, have you started the work? |
TristanCacqueray
added a commit
to TristanCacqueray/security-advisories
that referenced
this issue
Jul 24, 2023
TristanCacqueray
added a commit
to TristanCacqueray/security-advisories
that referenced
this issue
Jul 24, 2023
TristanCacqueray
added a commit
to TristanCacqueray/security-advisories
that referenced
this issue
Jul 24, 2023
TristanCacqueray
added a commit
to TristanCacqueray/security-advisories
that referenced
this issue
Jul 24, 2023
TristanCacqueray
added a commit
to TristanCacqueray/security-advisories
that referenced
this issue
Jul 24, 2023
TristanCacqueray
added a commit
to TristanCacqueray/security-advisories
that referenced
this issue
Jul 24, 2023
frasertweedale
pushed a commit
that referenced
this issue
Aug 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before we merge #88, we need to add regression tests for advisory parsing. Example-based tests will be fine, and we should test various success scenarios (in particular: presence/absence of optional fields) as well as common failure scenarios.
The text was updated successfully, but these errors were encountered: