-
Notifications
You must be signed in to change notification settings - Fork 186
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
Release 4.8.0 - Beta 2 - Wazuh UI regression testing #6446
Comments
Verify the app package installs and operates as expectedFixed an error pop-up spawn in MITRE ATT&CKChanged overview home top KPIsChange text in endpoint summary most active agent tooltipAdd the Vulnerabilities Detection application to the menu in Endpoints summary viewRemove the vulnerability pattern check in the health checkAdd cluster filter by default in vulnerabilities dashboard and inventory tab🟡 ChromeThe specific test of the pull request works fine, but when I tested the visualization filters they were lost when I changed between dashboard and inventory tabs. 🟡 FirefoxThe specific test of the pull request works fine, but when I tested the visualization filters they were lost when I changed between dashboard and inventory tabs. Check the existence of the index pattern of vulnerabilities states in Vulnerabilities Detection tabs🟢 Chrome✔️ Both tabs show a call with a warning when the Vulnerabilities module is disabled ✔️ If the index-pattern doesn't exist both tabs create it 🟢 Firefox✔️ Both tabs show a call with a warning when the Vulnerabilities module is disabled ✔️ If the index-pattern doesn't exist both tabs create it Add manager filter with cluster mode disabledChange the value to display in the Top 5 agents tableChanged most vulnerable endpoint labelExclude server filters on Vulnerabilities Detection > Dashboard and Inventory |
LGTM |
LGTM! |
The following issue aims to run manual tests for the current release candidate, report the results, and open new issues for any encountered errors.
Wazuh UI tests information
Test report procedure
TL;DR
All test results must have one the following statuses:
Any failing test must be properly addressed with a new issue, detailing the error and the possible cause.
It must be included in the
Problems
section of the current release candidate issue.Any expected fail or skipped test must be justified with a reason.
All auditors must validate the justification for an expected fail or skipped test.
An extended report of the test results must be attached as a zip, txt or images.
This report can be used by the auditors to dig deeper into any possible failures and details.
Test template
Test plan
Test
Conclusions
All tests have been executed and the results can be seen above.
Issues found:
Even though this was not part of the mentioned pull request, I found an unexpected behavior when using the visualization filters. I opened the following issue:
Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted to close this issue.
The text was updated successfully, but these errors were encountered: