Add alert.json to VD E2E test report
#5147
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
juliamagan
requested changes
Apr 1, 2024
|
Changelog updated in 380a641 |
Rebits
requested changes
Apr 1, 2024
juliamagan
approved these changes
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR aims to add the
alert.jsonfile to Vulnerability Detection E2E test report as well as theossec.logand the test logs are attached. This will be useful since when the test indicates that the alert has not been found, we will be able to check if the alert has been triggered or not. For this purpose, a new function has been added to obtain the alerts from thealert.jsonfile of the managers and the function in charge of collecting this information has been modified.Testing performed
In order to test the changes that have been made, the following environment has been released https://ci.wazuh.info/job/Wazuh_QA_environment/1025/. To avoid running the entire test and not spending so much time, only the
upgrade_package_remove_vulnerailitytest has been run, which is currently expected to fail due to what is reported in this issue #5104. When the test failed, a report was generated which indeed includes a file containing thealert.json, and is attached below:report5105.zip