Repository: wazuh/wazuh
Author: wazuhci
## End-to-End (E2E) Testing Guideline
- **Documentation:** Always consult the development documentation for the current stage tag at [this link](https://documentation-dev.wazuh.com/v4.14.5-rc1/index.html). Be careful because some of the description steps might refer to a current version in production, always navigate using the current development documentation for the stage under test. Also, visit the following [pre-release package guide](https://docs.google.com/document/d/1fW8koy8P8OMvcxzIOXWGDw9qmKlju-XuRHD-Bdv3uP4/edit) to understand how to modify certain links and urls for the correct testing of the development packages.
- **Test Requirements:** Ensure your test comprehensively includes a full stack and agent/s deployment as per the Deployment requirements, detailing the machine OS, installed version, and revision.
- **Deployment Options:** While deployments can be local (using VMs, Vagrant, etc) or on the aws-dev account, opt for local deployments when feasible. For AWS access, coordinate with the DevOps team through [this link](https://github.com/wazuh/internal-devel-requests/issues/new?assignees=&labels=level%2Ftask%2C+request%2Foperational%2C+type%2Fchange&projects=&template=operational--request.md&title=%3CTitle%3E).
- **External Accounts:** If tests require third-party accounts (e.g., GitHub, Azure, AWS, GCP), request the necessary access through the DevOps team [here](https://github.com/wazuh/internal-devel-requests/issues/new?assignees=&labels=level%2Ftask%2C+request%2Foperational%2C+type%2Fchange&projects=&template=operational--request.md&title=%3CTitle%3E).
- **Alerts:** Every test should generate a minimum of one end-to-end alert, from the agent to the dashboard, irrespective of test type.
- **Multi-node Testing:** For multi-node wazuh-manager tests, ensure agents are connected to both workers and the master node.
- **Package Verification:** Use the pre-release package that matches the current TAG you're testing. Confirm its version and revision.
- **Filebeat Errors:** If you encounter errors with Filebeat during testing, refer to [this Slack discussion](https://wazuh-team.slack.com/archives/C03BDG0K6JC/p1672168163537809) for insights and resolutions.
- **Known Issues:** Familiarize yourself with previously reported issues in the Known Issues section. This helps in identifying already recognized errors during testing.
- **Reporting New Issues:** Any new errors discovered during testing that aren't listed under Known Issues should be reported. Assign the issue to the corresponding team (QA if unsure), add the `Release testing` objective and `Urgent` priority. Communicate these to the team and QA via the c-release Slack channel.
- **Test Conduct:** It's imperative to be thorough in your testing, offering enough detail for reviewers. Incomplete tests might necessitate a redo.
- **Documentation Feedback:** Encountering documentation gaps, unclear guidelines, or anything that disrupts the testing or UX? Open an issue, especially if it's not listed under Known Issues. Please answer the feedback section, this is a mandatory step.
- **Format:** If this is your first time doing this, refer to the format (but not necessarily the content, as it may vary) of previous E2E tests, here you have an example https://github.com/wazuh/wazuh/issues/13994.
- **Status and completion:** Change the issue status within your team project accordingly. Once you finish testing and write the conclusions, move it to Pending review and notify the @wazuh/devel-xdrsiem-server-div2 team via Slack using the [c-release channel](https://wazuh-team.slack.com/archives/C02A737S5MJ). Beware that the reviewers might request additional information or task repetitions.
- **For reviewers:** Please move the issue to Pending final review and notify via Slack using the same thread if everything is ok, otherwise, perform an issue update with the requested changes and move it to On hold, increase the review_cycles in the team project by one and notify the issue assignee via Slack using the same thread.
For the conclusions and the issue testing and updates, use the following legend:
**Status legend**
- 🟢 All checks passed
- 🟡 Found a known issue
- 🔴 Found a new error
## Issue delivery and completion
- **Initial delivery:** The issue's assignee must complete the testing and deliver the results by Apr 20, 2026 and notify the @wazuh/devel-xdrsiem-server-div2 team via Slack using the [c-release channel](https://wazuh-team.slack.com/archives/C02A737S5MJ)
- **Review:** The @wazuh/devel-xdrsiem-server-div2 team will assign a reviewer and add it to the `review_assignee` field in the project. The reviewer must then review the test steps and results. Ensure that all iteration cycles are completed by Apr 21, 2026 date (issue must be in `Pending final review` status) and notify the QA team via Slack using the [c-release channel](https://wazuh-team.slack.com/archives/C02A737S5MJ).
- **Auditor:** The QA team must audit, validate the results, and close the issue by Apr 22, 2026.
## Deployment requirements
| Component | Installation | Type | OS |
|----------|--------------|------|----|
| Indexer | [Installation assistant](https://documentation-dev.wazuh.com/v4.14.5-rc1/installation-guide/wazuh-indexer/installation-assistant.html) | Multi node | Ubuntu 24.04 x86_64 |
| Server | [Installation assistant](https://documentation-dev.wazuh.com/v4.14.5-rc1/installation-guide/wazuh-server/installation-assistant.html) | Single node | Ubuntu 22.04 x86_64 |
| Dashboard | [Installation assistant](https://documentation-dev.wazuh.com/v4.14.5-rc1/installation-guide/wazuh-dashboard/installation-assistant.html) | - | Ubuntu 24.04 aarch64 |
| Agent | [Wazuh WUI one-liner deploy using IP and GROUP (created beforehand, don't use default)](https://documentation-dev.wazuh.com/v4.14.5-rc1/_images/deploy-new-agent-from-ui1.png) | - | Ubuntu 24.04 x86_64 |
## External resources
No external resouces needed.
## Test description
Follow and complete the documentation steps and the examples, ensuring the access is adequate based on each requirement:
https://documentation-dev.wazuh.com/v4.14.5-rc1/user-manual/user-administration/rbac.html?highlight=RBAC
Once the roles have been configured, let's check that they work correctly:
1. Log in with admin
2. Check that you can do everything an admin can (basically everything, add agents, edit configuration, create groups, delete agents).
3. Log out.
4. Log in with read-only.
5. Check that you only have read-only permissions:
- Access each Server management menu and check that you only have read permissions, that is, you cannot delete, edit, add anything, or perform any action.
- Access each Indexer management menu and check that you only have read permissions, that is, you cannot delete, edit, add anything, or perform any action.
- Access each Dashboard management menu and check that you only have read permissions, that is, you cannot delete, edit, add anything, or perform any action.
## Known issues
There are no known issues.
## Conclusions
Summarize the errors detected (Known Issues included). Illustrate using the table below. **REMOVE CURRENT EXAMPLES**:
| **Status** | **Test** | **Failure type** | **Notes** |
|----------------|-------------|---------------------|----------------|
| 🟡 | Example Test: API Integration | Timeout issues on certain endpoints | Known issue: https://github.com/example/repo/issues/12345 |
| 🔴 | Example Test: Data Migration | Data inconsistency in the new version | New issue opened: https://github.com/example/repo/issues/67890 |
## Feedback
We value your feedback. Please provide insights on your testing experience.
- Was the testing guideline clear? Were there any ambiguities?
- **RESPONSE HERE**
- Did you face any challenges not covered by the guideline?
- **RESPONSE HERE**
- Suggestions for improvement:
- **RESPONSE HERE**
## 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.
- [ ] @juliamagan
- [ ] @wazuh/devel-xdrsiem-server-div2