-
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.6.0 - Alpha 1 - E2E UX tests - Demo environment #18843
Comments
Update report
Red Hat Wazuh agent
|
Analysis reportCheck that there are no errors in manager, agent, cluster, indexer and dashboard logsWazuh agent - Ubuntu 22.04.2 LTS
Wazuh agent - Red Hat 9
Wazuh agent - CentOS 8
Wazuh agent - Windows Server 2019 Datacenter
Wazuh agent - Debian 11
Wazuh agent - Amazon Linux 2
Wazuh dashboard - Amazon Linux 2
Amazon Linux 2 - Wazuh indexer - node3
Amazon Linuz 2 - Wazuh indexer - node2
Amazon Linux 2 - Wazuh indexer - node1
Wazuh server - master - env1
Wazuh server - master - env2
Wazuh server - worker - env1
|
Analysis reportCheck that wazuh daemons are running with the expected user.Wazuh agent - Ubuntu 22.04.2 LTS
Wazuh agent - Red Hat 9
Wazuh agent - CentOS 8
Wazuh agent - Windows Server 2019 Datacenter
Wazuh agent - Debian 11
Wazuh agent - Amazon Linux 2
Wazuh dashboard - Amazon Linux 2
Amazon Linux 2 - Wazuh indexer - node3
Amazon Linuz 2 - Wazuh indexer - node2
Amazon Linux 2 - Wazuh indexer - node1
Wazuh server - master - env1
Wazuh server - master - env2
Wazuh server - worker - env1
Note
|
Analysis reportCheck that the status of the indexer cluster is the expected.Amazon Linux 2 - Wazuh indexer - node3
|
Analysis reportCheck that there are no errors in the browser's developer console when browsing the App.Wazuh dashboard WUI
|
Blocked by https://github.com/wazuh/wazuh-automation/issues/1283 There are 13,371,724 alerts from
|
Analysis reportCheck that there are alerts for each of the modules configured.
env-1 node
env-2 node
Reported at: #18946 Due to this it is not possible to continue analyzing the environment and the analysis will be completed in the next testing iteration, the environment is available for investigation. |
Analysis reportCheck that no warning symbols appear in the browser's developer console when browsing the App.Done in #18843 (comment) |
The environment seems to be working fine. It was requested to @rauldpm to provide evidence for the remaining items:
|
Analysis reportThe environment is still in a defective state Check that there are alerts for each of the modules configured.Images provided by @teddytpc1Generate an alert and check that this alert appears in the dashboard (end to end)This task will not done since it implies modifying the Wazuh manager configuration, in the next step it is observed that there are alerts generated Check that the search engine works without specifying a field and using * |
LGTM! |
End-to-End (E2E) Testing Guideline
For the conclusions and the issue testing and updates, use the following legend:
Status legend
Deployment requirements
Test description
Test demo.wazuh.info environment:
To access the demo environment, please contact @cicd-team.
Known issues
More
menu wazuh-dashboard-plugins#4074Conclusions
Summarize the errors detected (Known Issues included). Illustrate using the table below, removing current examples:
Feedback
We value your feedback. Please provide insights on your testing experience.
Reviewers validation
The criteria for completing this task is based on the validation of the conclusions and the test results by all reviewers.
All the checkboxes below must be marked in order to close this issue.
The text was updated successfully, but these errors were encountered: