-
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 6 - Wazuh UI regression testing #6616
Labels
Comments
Verify the app package installs and operates as expectedCreate published vulnerabilities severity visualization #6583Remove hardcoded colors and implement OUI styles #6587Add JSON visualization to Vulnerability Detection inventory flyout #6590Change getHistory for syncHistoryLocations #6591🟢 ChromeThe overview after login must be rendered once and must not have repeated requests to opensearch. Navigate between dashboards with the events tab and without the events tab, navigation should work correctly. |
LGTM |
Although the issue found is not related to the tests, it is a new one, so the conclusion should be 🔴 |
LGTM |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 of 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 mentioned tests have been executed and the results can be seen above.
We found an issue when accessing a disconnected agent log collection configuration. This is not related to the tests made but should be addressed.
Issue found:
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: