-
Notifications
You must be signed in to change notification settings - Fork 32
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
E2E tests: Local debugging and testing #3166
Comments
T1: Run a test using an invalid hostname in the inventory 🔴Conclusion
Tester: @BelenValdivia 🔴
Result 🔴The test fails but the validation stage does not check that the name of the hosts follows the E2E standard: Tester: @juliamagan 🔴
Result 🔴The test fails because the group name is invalid, but it wasn't checked. Tester: @mauromalara 🔴
Result 🔴The test fails but the validation stage does not check that the name of the hosts follows the E2E standard:
|
T2: Run a test using an invalid IP in the inventory 🟡Conclusion
Tester: @BelenValdivia 🟡
Result 🟢The validation stage checks that the IP of the host is invalid Tester: @juliamagan 🟡
Result 🟡The validation stage checks that the IP of the host is invalid, but the error is not correctly displayed. Tester: @mauromalara 🟡
Result 🟡The validation stage checks that the IP of the host is invalid, but the error is not correctly displayed. |
T3: Run a test using an invalid indexer password in the inventory 🟡Conclusion
Tester: @BelenValdivia 🟡
Result 🟡401 Unauthorized response from indexer. We could check this in the validation phase. Tester: @juliamagan 🟡
Result 🟡The API request fails as expected, but maybe, we could check this in the validation phase. Tester: @mauromalara 🟡
Result 🟡The API request fails as expected, but maybe, we could check this in the validation phase. |
T4: Run 2 tests with different environments 🟢Conclusion
Tester: @BelenValdivia 🟢
Result 🟢Both tests passed Tester: @juliamagan 🟢
Result 🟢Both tests passed Tester: @mauromalara 🟢
Result 🟢All tests have passed successfully. |
T5: Run 2 tests with the same environment 🟢Conclusion
Tester: @BelenValdivia 🟢
Result 🟢Both tests passed. Report: T5-3166-e2e-belenvaldivia.zip Tester: @juliamagan 🟢
Result 🟢Both tests passed. Tester: @mauromalara 🟢
Result 🟢Both tests have passed. |
T6: Run 1 test (with more than 1 test case) selecting 1 test case (-k) 🔴Conclusion
Tester: @BelenValdivia 🟢
Result 🟢The specific test case passed Tester: @juliamagan 🟢
Result 🟢The specific test case passed Tester: @mauromalara 🔴
Result 🔴The test has failed, the failure must be researched. |
T7: Run all tests but select only 1 test (-k) 🟢Conclusion
Tester: @BelenValdivia 🟢1. Launch all tests but select just one: `test_suricata_integration` 2. Command:
Result 🟢The specific test passed Tester: @juliamagan 🟢
Result 🟢The specific test passed Tester: @mauromalara 🟢
Result 🟢The specific test passed |
T8: Run a test with an unsupported Linux distribution installed in a target host 🔴Conclusion
Tester: @BelenValdivia 🟢1. Force the error. Define a Centos agent in the Inventory but the host is a Ubuntu agent.
Result 🟢The validation stage checks the incorrect Linux distribution installed in a target host. Tester: @juliamagan 🔴
Result 🔴The distribution wasn't checked in the validation phase, so the test was launched and failed. Tester: @mauromalara 🟢
Result 🟢The validation works as expected. |
T9: Run a test in a target host with an incorrect OS 🟡Conclusion
Tester: @BelenValdivia 🟢1. Force the error in the Inventory. Define a CentOS agent but the host is a Windows agent
Result 🟢The test fails but the validation stage does not check the incorrect OS defined in the inventory Tester: @juliamagan 🟢
Result 🟢The OS was checked in the validation phase and failed, so the test wasn't launched. Tester: @mauromalara 🟡
Result 🟡The validation phase fails, but it does not check the OS, instead, it fails while gathering Ansible facts. |
T10: Run a test in a target host with the manager service stopped 🟡Conclusion🟡: All executions were run successfully, but @mauromalara detect that the validation stage does not include the validation for a Windows agent service.
Tester: @BelenValdivia 🟢1. Force the error by stopping the Wazuh manager.
Result 🟢The test fails, the validation stage checks that the Wazuh manager is stopped Tester: @juliamagan 🟢
Result 🟢It is checked that the manager should be running correctly, so the test isn't launched. Tester: @mauromalara 🟢
Result 🟢 |
T11: Run all test cases from the E2E folder 🔴Conclusion
Tester: @BelenValdivia 🔴1. Launched every tests:
Result 🔴The following tests should not have failed:
Tester: @juliamagan 🔴
Result 🔴The following tests should not have failed:
Tester @mauromalara 🔴
Result 🔴The following tests have failed:
|
T12: Run all tests that require Linux 🔴Conclusion
Tester: @BelenValdivia 🔴1. Run all tests that require Linux as follows:
Result 🔴We can't run our tests using markers because this feature isn't implemented yet. Tester: @juliamagan 🔴
Result 🔴We can't run our tests using markers because this feature isn't implemented yet. Tester: @mauromalara 🔴
Result 🔴We can't run our tests using markers because this feature isn't implemented yet. |
T13: Run all tests that require Windows 🔴Conclusion
Tester: @BelenValdivia 🔴1. Run all tests that require Windows as follows:
Result 🔴We can't run our tests using markers because this feature isn't implemented yet. Tester: @juliamagan 🔴
Result 🔴We can't run our tests using markers because this feature isn't implemented yet. Tester: @mauromalara 🔴
Result 🔴We can't run our tests using markers because this feature isn't implemented yet. |
T14: Run a test without specifying the inventory 🟢Conclusion
Tester: @BelenValdivia 🟢1. Run the test without specifying the inventory:
Result 🟢Nothing is launched because there is no inventory Tester: @juliamagan 🟢
Result 🟢Nothing is launched because there is no inventory Tester: @mauromalara 🟢
Result 🟢No test was executed because there is no inventory. |
T15: Run all tests but unselect tests (-k not) 🔴Conclusion
Tester: @BelenValdivia 🔴1. Launched every test except `test_yara_integration`:
Result 🔴The following tests should not have failed:
Tester: @juliamagan 🔴
Result 🔴The following tests should not have failed:
Tester: @mauromalara 🔴
Result 🔴
|
Description
After the development of the tests in #2872 and the improvements made in later tasks, the tests are ready to be merged into the numbered branch, but first, we must make sure that they are fully functional and there are no errors. To do this, all the people involved in this development must launch several runs of these tests and that the result of all of them is successful.
Previous requirements
Environment
Inventory
inventory.yaml
Packages
Execution
Proposed use cases
-k
)-k
)-k not
)Open issues
The text was updated successfully, but these errors were encountered: