-
Notifications
You must be signed in to change notification settings - Fork 32
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
QA testing - Test new MSU feed adds new hotfixes values #3360
Comments
4 tasks
Review data
Testing environment
Tested packages
Status
Conclusion 🟢Vulnerability detector works correctly with the new msu feed. New data was detected as expected. The new feed has 120k+ rows in |
Task ResultsRun IT tests to check that Vulnerability Detector test suite works correctly 🟢
Check that new MSU has more rows on in cve.db 🟢
<!-- Windows OS vulnerabilities -->
<provider name="msu">
<enabled>yes</enabled>
<path>/vagrant/msu.json</path>
<update_interval>1h</update_interval>
</provider>
Conclusion: After using the new feed, the DB shows 120k+ |
Deblintrake09
changed the title
QA testing - Test new MSU hotfixes
QA testing - Test new MSU feed adds new hotfixes values
Sep 26, 2022
🟢 Everything seems to be working properly |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This manual testing aims to verify the proper functioning of the new MSU feed's changes. The PR adds a series of Patches and Supercedence information. This data currently has no related vulnerabilities so they cannot be actually tested on an OS, this would need to be tested on an automated test, since there is need to add a custom feed, custom packages and patches in the agent (This will be handled in the test development issue).
Proposed checks
Steps to test
MSU
andMSU_SUPERSEDENCE
Considerations
Since this is an update of the MSU Feed and not of the application, there will be no Fresh/Update tests. The manual testing done will check that the
cve.db
DB has more content in theMSU_SUPERSEDENCE
table, compared with the current feed.The text was updated successfully, but these errors were encountered: