Skip to content
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

Closed
1 task done
asteriscos opened this issue Apr 24, 2024 · 4 comments
Closed
1 task done

Release 4.8.0 - Beta 6 - Wazuh UI regression testing #6616

asteriscos opened this issue Apr 24, 2024 · 4 comments
Assignees
Labels
level/task Task issue type/test Test issue

Comments

@asteriscos
Copy link
Member

asteriscos commented Apr 24, 2024

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

Main release candidate issue wazuh/wazuh#23005
Version 4.8.0
Release candidate # Beta 6
Tag v4.8.0-2.10.0-beta6
Previous UI regression tests issue #6582

Test report procedure

TL;DR

  1. The specified tests will be executed in every platform and version mentioned in this issue.
  2. Include evidence of each test performed.
  3. Report any problem or bug. Open a new issue for each of them and link them here.
  4. Justify skipped tests.

All test results must have one of the following statuses:

Doesn't apply
The test hasn't started yet.
🟢 All checks passed.
🔴 There is at least one failed check.
🟡 There is at least one expected fail or skipped test and no failures.

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 Chrome Firefox Safari
-

Test plan

  1. Verify the app package installs and operates as expected.
  2. Create published vulnerabilities severity visualization #6583
  3. Remove hardcoded colors and implement OUI styles #6587
  4. Add JSON visualization to Vulnerability Detection inventory flyout #6590
  5. Change getHistory for syncHistoryLocations #6591

Test

Test Chrome Firefox Safari
Verify the app package installs and operates as expected 🟢 🟢
Create published vulnerabilities severity visualization #6583 🟢 🟢
Remove hardcoded colors and implement OUI styles #6587 🟢 🟢
Add JSON visualization to Vulnerability Detection inventory flyout #6590 🟢 🟢
Change getHistory for syncHistoryLocations #6591 🟢 🟢

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.

@asteriscos asteriscos added type/test Test issue level/task Task issue labels Apr 24, 2024
@asteriscos asteriscos self-assigned this Apr 24, 2024
@wazuhci wazuhci moved this to In progress in Release 4.8.0 Apr 24, 2024
@asteriscos
Copy link
Member Author

asteriscos commented Apr 24, 2024

Verify the app package installs and operates as expected

🟢 Chrome

image

🟢 Firefox

image

Create published vulnerabilities severity visualization #6583

🟢 Chrome

image

🟢 Firefox

image

Remove hardcoded colors and implement OUI styles #6587

🟢 Chrome

image

image

image

image

🟢 Firefox

image

image

image

image

Add JSON visualization to Vulnerability Detection inventory flyout #6590

🟢 Chrome

image

🟢 Firefox

image

Change getHistory for syncHistoryLocations #6591

🟢 Chrome

The overview after login must be rendered once and must not have repeated requests to opensearch.

Peek 2024-04-24 14-53

Navigate between dashboards with the events tab and without the events tab, navigation should work correctly.

Peek 2024-04-24 15-01

🟢 Firefox

The overview after login must be rendered once and must not have repeated requests to opensearch.

Peek 2024-04-24 14-58

Navigate between dashboards with the events tab and without the events tab, navigation should work correctly.

Peek 2024-04-24 15-00

@wazuhci wazuhci moved this from In progress to Pending review in Release 4.8.0 Apr 24, 2024
@Tostti
Copy link
Member

Tostti commented Apr 24, 2024

LGTM

@wazuhci wazuhci moved this from Pending review to Pending final review in Release 4.8.0 Apr 24, 2024
@juliamagan
Copy link
Member

Although the issue found is not related to the tests, it is a new one, so the conclusion should be 🔴

@juliamagan
Copy link
Member

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/test Test issue
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants