-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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.10.0 - Alpha 3 - Wazuh UI regression testing #26781
Comments
Legend: Test 🟢
|
Test 🔴
Test plan
EvidenceGrabacion.2024-11-13.100307.mp4 |
Test 🔴
Test plan
EvidenceGrabacion.de.pantalla.2024-11-13.a.la.s.11.27.11.a.m.movEvidenceGrabacion.de.pantalla.2024-11-13.a.la.s.11.34.57.a.m.movEvidenceGrabacion.2024-11-13.100307.mp4EvidenceGrabacion.de.pantalla.2024-11-13.a.la.s.1.52.40.p.m.movGrabacion.de.pantalla.2024-11-13.a.la.s.1.49.38.p.m.mov |
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 🔴
Test plan
Conclusions 🔴
Some of the tests failed and additionally, there's a specific issue with Safari.
Issues created:
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 in order to close this issue.
The text was updated successfully, but these errors were encountered: