Wazuh installation assistant integration tests

[c-bordon]

Related

https://github.com/wazuh/wazuh-automation/issues/2940

Description

Integration tests

Integration test suites should be defined for each of the Installation Assistant tools (wazuh-certs-tool, wazuh-passwords-tool, and wazuh-install). Each suite must validate that the corresponding tool works correctly end to end, including both successful and error scenarios.

wazuh-install integration tests

• Verify integration tests for the following installation modes:

  • AIO (All-in-One) installation
  • Distributed installation
  • Offline installation

• For each installation mode test

  • ARM/AMD
  • RPM/DEB

• For each installation mode, validate

  • The status of the services
  • That certificates are located in the correct paths
  • Connectivity between components
  • Access for Wazuh API users and Indexer internal users
  • Access to the dashboard

Note

Verify expected failures when required installation prerequisites are not met

Unit tests

Unit test must remain in the wazuh-installation-assistant repository, this test need to validate the code structure and the correctness of each method and function.

Note

Since the codebase is written in Bash, using a comprehensive testing framework like those available for other programming languages is more challenging. However, the BATS library can be used to implement these unit tests effectively.

Important

It is important to note that there are currently tests under the tests/ directory, but they are outdated and not compatible with the new codebase. As a result, it is recommended to create the tests from scratch, using the existing tests only as a reference for the type of validations that were previously performed.

[fcaffieri]

Important

In this issue [https://github.com//issues/589], the complete flow and architecture of the integration test workflow for wazuh-installation-assistant and the tools wazuh-cert-tool and wazuh-password-tool were developed.
Due to the need to completely rework the unit tests and create integration tests by reusing the test module from the wazuh-automation repository, it was necessary to design and generate the complete test flow and architecture to unify all tests that use the same pattern.

In this pull request, all necessary modifications were applied to the test module. These are listed below:

1. New scopes for module execution at 3 levels:
   a. --test-type: Type of test to run (ami, ova, installer, cert-tool, passwords-tool). The test type determines which test file and checks are executed (certificate tests, service tests, password tests, etc.).

b. --deployment-type: Defines the infrastructure type of the target environment. Possible values (easily expandable): installer, Ansible, Kubernetes. This controls how services, certificates, and paths are resolved for that environment.

c. --component-type: Filters tests to a specific Wazuh component. Possible values: all (default), indexer, manager, dashboard. When not set, all available components are tested.

2. Additionally, a --profile option allows passing a YAML file with field overrides applied on top of the deployment profile, enabling fine-grained customization without modifying code.

In this other pull request (PR) (#630), the following changes were made:

1. Refactoring of unit tests related to all tools (assistant, wazuh cert tool, wazuh password tool).
2. Add a hatch to execute the unit test.
3. Create a WF for unit test execution on any PR in "ready for review" state.
4. Creation of the complete workflow for integration tests, which has the following architecture:
   a. Manual execution of the test.
   b. Execution via commands in the PR comments. For execution via commands, the commands it accepts are: "/test-install", "/test-cert-tool", "/test-password-tool", and "/test-assistant" (the latter tests all the previous ones).
5. Generation of a matrix for parallel execution of integration tests on all the representative operating systems supported.

---

So, with these changes already applied, the only remaining step in this issue is to correct the AIO installation assistant tests and add the distributed tests, if required.
To do this, you need to edit the WF .github/workflows/check_integration_tools.yaml file to override the default configuration set in the test module, using the correct component names, path configurations, etc. This requires generating a YAML file (see the "YAML Profile Overrides" section of integration-test-module/README.md) and passing it to the test module with the --profile parameter.