-
Notifications
You must be signed in to change notification settings - Fork 30
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
Additional E2E Tests for Vulnerability Detector #4914
Comments
Refactored TestInitialScans in order to include |
|
It has been detected a new error in vulnerability detection module. Expected alerts was not triggered. In addition only the mitigated alerts is different of the previously alerted vulnerability. Currently working in replicating this issue with debug option enabled:
|
On hold in favor of Beta 4 testing |
A bug that affects
|
|
|
|
Unblocked. Continuing with #5266 development |
Finish refactor of Some of the test cases fail:
Note Test performed in a limited environment of 1 agent. |
Open PR Draft with additional changes: https://github.com/wazuh/wazuh-qa/pull/5287/files Todo
|
Tests in the Jenkins pipeline have unexpectedly failed with no accompanying reports generated. Check here: https://ci.wazuh.info/job/Test_e2e_system/265/console Investigating further; moving the issue to 'In Progress' to resolve |
Tests were launched again after PR requested changes: Where we can see the following errors:
Further research is required |
Description
In the development of vulnerability detector E2E tests, we introduced new test cases to cover specific scenarios that were not part of the original plan.
This issue is created to track the development of these additional tests, which were not part of the initial plan. Additionally, the steps to manually reproduce these tests will be provided in this issue to facilitate progress for the Beta 2 Release.
Tests cases
Tests Design
Installation of a vulnerable package when agent is offline
Enable vulnerability detector when some agents are already registered
Change agents' manager and install a vulnerable package
The text was updated successfully, but these errors were encountered: