Closed davidjiglesias closed 5 months ago
Requested access for Demo Environment: https://github.com/wazuh/internal-devel-requests/issues/1204
The available machines are:
curl -k -u ADMIN_USER:PASS https://indexer_IP:9200/_cat/nodes?v
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role node.roles cluster_manager name
x.x.x.x 32 90 0 0.01 0.03 0.02 dimr cluster_manager,data,ingest,remote_cluster_client - node-7
x.x.x.x 37 93 0 0.00 0.00 0.00 dimr cluster_manager,data,ingest,remote_cluster_client - node-1
x.x.x.x 19 92 0 0.00 0.00 0.00 dimr cluster_manager,data,ingest,remote_cluster_client * node-3
x.x.x.x 24 93 0 0.00 0.00 0.00 dimr cluster_manager,data,ingest,remote_cluster_client - node-2
End-to-End (E2E) Testing Guideline
Release testing
objective andVery high
priority. Communicate these to the team and QA via the c-release Slack channel.For the conclusions and the issue testing and updates, use the following legend:
Status legend
Issue delivery and completion
review_assignee
field in the project. The reviewer must then review the test steps and results. Ensure that all iteration cycles are completed by Jun 02, 2024 date (issue must be inPending final review
status) and notify the QA team via Slack using the c-release channel.Deployment requirements
Test description
Test demo.wazuh.info environment:
To access the demo environment, please contact @devel-devops.
Known issues
Conclusions :red_circle:
Summarize the errors detected (Known Issues included). Illustrate using the table below. REMOVE CURRENT EXAMPLES:
Virus Total
SettingFeedback
We value your feedback. Please provide insights on your testing experience.
Several sections need to be clearer, and some lack essential instructions. For instance, it should be explicitly stated that Docker must be provisioned manually in certain environments and that agents must be configured to generate this kind of alert.
Additionally, the current structure is prone to errors. Take, for example, the instruction "Check that the Wazuh daemons are running with the expected user." If the expected users are not clearly specified, testers might use the previous stage or release as a reference point, which could lead to potential issues.
The number of known issues related to console errors is too vast, making it difficult to determine which errors are expected and which are not. Additionally, many errors originate from the client side, further complicating the task and making it time-consuming.
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.