-
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
Health check of the vulnerability detector tests after the new development added in 4.3
#2451
Comments
Testing reportTesting parameters
Testing status
|
Looking at the results obtained, there are tests that are already disabled because they have been deprecated or malfunctioned. However, there are others that have failed in some executions, causing false positives, or fail always. Also, it has been concluded that feed tests can be unstable, depending on which tests have been previously run on that machine. Therefore, it has been decided to disable all of them, for future research and refactoring. The tests that must be disabled in order to have the initial "full green" are shown below.
|
After the merge of the following developments wazuh/wazuh#7749 and wazuh/wazuh#8727 corresponding to the vulnerability detector module for 4.3, it was necessary to update the integration tests.
These tests were updated in the following PR: #1243
The following is requested:
Tasks
dev-cves-alerts-inventory
branch with all changes from themaster
branch. Conflicts should be fixed.The final objective is to evaluate the general state of the vulnerability detector tests applying the new changes introduced in
4.3
.The text was updated successfully, but these errors were encountered: