You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #5106, during the tests executed for 4.8.0 Beta 4, in wazuh/wazuh#22493, it has been observed that the tests are marked as passed even if there were errors when parsing the vulnerabilities. This behavior has been found specifically in tests_syscollector_first_second_scan_consistency_index.
We should adjust the code so that if there are any errors during the test, the test fails for that host and only continues on the hosts that have not failed. It should also be marked as failed.
It has been decided that this is an uncommon error to appear from an internal tool for testing, that it makes sense that if it fails, it will affect the rest of the tests, so it is not necessary to include the logic that allows moving forward with the rest of the hosts if it fails here. Solved in #5146 from #5106.
Description
Related to #5106, during the tests executed for 4.8.0 Beta 4, in wazuh/wazuh#22493, it has been observed that the tests are marked as passed even if there were errors when parsing the vulnerabilities. This behavior has been found specifically in
tests_syscollector_first_second_scan_consistency_index
.We should adjust the code so that if there are any errors during the test, the test fails for that host and only continues on the hosts that have not failed. It should also be marked as failed.
Report: Test_e2e_system_244_test_vulnerability_detector.zip
The text was updated successfully, but these errors were encountered: