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 - Release Candidate 2 - Wazuh UI regression testing #6668

Closed
1 task done
asteriscos opened this issue May 14, 2024 · 4 comments
Closed
1 task done

Release 4.8.0 - Release Candidate 2 - Wazuh UI regression testing #6668

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

Comments

@asteriscos
Copy link
Member

asteriscos commented May 14, 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#23405
Version 4.8.0
Release candidate # RC2
Tag v4.8.0-2.10.0-rc2
Previous UI regression tests issue #6640

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. Change flyout title to Vulnerability details
  3. Hide vulnerabilities global filter editor button
  4. Fix inventory table fullscreen styles
  5. Change vulnerabilities implicit filter field to wazuh.cluster.name
  6. Change vulnerabilities default index pattern

Test

Test Chrome Firefox Safari
Verify the app package installs and operates as expected 🟢 🟢
Change flyout title to Vulnerability details 🟢 🟢
Hide vulnerabilities global filter editor button 🟢 🟢
Fix inventory table fullscreen styles 🟡 🟡
Change vulnerabilities implicit filter field to wazuh.cluster.name 🟢 🟢
Change vulnerabilities default index pattern 🟢 🟢

Conclusions 🔴

The tests have been conducted almost entirely successfully, except for one that contains an error that has not been reproducible or is not frequent. The information regarding the tests can be verified below.

But I found this problem #6668 (comment), this will become an issue to be fixed in a future stage.

I created the following issue to fix it in the next stage.

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 May 14, 2024
@wazuhci wazuhci moved this to Backlog in Release 4.8.0 May 14, 2024
@JuanGarriuz JuanGarriuz self-assigned this May 15, 2024
@wazuhci wazuhci moved this from Backlog to In progress in Release 4.8.0 May 15, 2024
@JuanGarriuz
Copy link
Member

JuanGarriuz commented May 16, 2024

Test Chrome Firefox Safari
Verify the app package installs and operates as expected 🟢 🟢
Change flyout title to Vulnerability details 🟢 🟢
Hide vulnerabilities global filter editor button 🟢 🟢
Fix inventory table fullscreen styles 🟡 🟡
Change vulnerabilities implicit filter field to wazuh.cluster.name 🟢 🟢
Change vulnerabilities default index pattern 🟢 🟢
Verify the app package installs and operates as expected 🟢
  • Chrome

image

  • Firefox

image

Change flyout title to Vulnerability details 🟢
  • Chrome

image
image
image

  • Firefox

image
image
image

Hide vulnerabilities global filter editor button🟢
  • Chrome

image

image

-Firefox

image

image

Fix inventory table fullscreen styles 🟡

Sometimes the navigation dock doesn't work properly, the right side of the menu stays in a gray tone and the menu doesn't lock. I haven't been able to capture the error or figure out how to reproduce it, but it has also happened to other colleagues.

  • Chrome

image
image
image
image

  • Firefox

image
image
image
image

Change vulnerabilities implicit filter field to wazuh.cluster.name 🟢
  • Chrome

image
image

  • Firefox

image
image

Change vulnerabilities default index pattern 🟢
  • Chrome

image
image
image

  • Firefox

image
image
image

@wazuhci wazuhci moved this from In progress to Pending review in Release 4.8.0 May 16, 2024
@JuanGarriuz
Copy link
Member

JuanGarriuz commented May 17, 2024

In the Discover plugin, I see a warning about the Discover legacy version.
It should have been already fixed, we must check this.

image

@wazuhci wazuhci moved this from Pending review to In review in Release 4.8.0 May 17, 2024
@asteriscos
Copy link
Member Author

LGTM ✔️

@wazuhci wazuhci moved this from In review to Pending final review in Release 4.8.0 May 17, 2024
@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