forked from wazuh/wazuh-docker
Jesus Garcia
f04ed6e608
--- - All relevant content of README.md files was migrated to docs/ section in their respective section. - These README files has been deleted (4 files) - All README.md files (additional to the project's root and docs/) have been edited. --- - Both files build-docker-images/README.md and docs/dev/build-image.md have almost same content, so it was discarded the README file - As the directory and docker image are going to be disused, the certs-gen documentation contents of indexer-certs-creator/README.md was not mig> - The 'bash' command added to the docs/dev/build-image.md was removed - Added workflow usage docs file to the the SUMMARY.md file --- - Removed '$' parameter and added 'bash' to all markdown code blocks headings (```) ---
31 lines
1.2 KiB
Markdown
31 lines
1.2 KiB
Markdown
# Pull Request Test Execution
|
|
|
|
This repository includes automated tests designed to validate the correct deployment of Wazuh using Docker. These tests are executed on every pull request (PR) to ensure the integrity and stability of the system when changes are introduced.
|
|
|
|
Check more information on the [Workflow usage](workflow-usage.md) page.
|
|
|
|
## Purpose
|
|
|
|
The main objective of the tests is to verify that the Wazuh Docker environment can be successfully deployed and that all its core components (Wazuh Manager, Indexer, Dashboard, and Agents) operate as expected after any modification in the codebase.
|
|
|
|
## When Tests Run
|
|
|
|
- Tests are automatically triggered on every pull request (PR) opened against the repository.
|
|
- They also run when changes are pushed to an existing PR.
|
|
|
|
## What Is Tested
|
|
|
|
The tests aim to ensure:
|
|
- Successful build and startup of all Docker containers.
|
|
- Proper communication between components (e.g., Manager ↔ Indexer, Dashboard ↔ API).
|
|
- No critical errors appear in the logs.
|
|
- Key services are healthy and accessible.
|
|
|
|
## Benefits
|
|
|
|
- Reduces the risk of breaking the deployment flow.
|
|
- Ensures system consistency during feature development and refactoring.
|
|
- Provides early feedback on integration issues before merging.
|
|
|
|
---
|