-
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
Add a test to check that the queue socket remains after a configuration test #1850
Comments
The working branch for this issue is: 1850-check-queue-socket-status-test |
As for now, there is a first approach for the requested test already implemented. The implementation checks if the Inode value and the File Time value of the queue socket change when the command |
QA-docs executiontest_queue_socket_properties
Results2022-01-17 12:57:20,028 - INFO - Looking for test_queue_socket_properties.py 2022-01-17 12:57:20,129 - INFO - Run completed, documentation location: /home/mauro/Documents/Wazuh/wazuh-qa/deps/wazuh_testing/venv/lib/python3.8/site-packages/wazuh_testing-4.3.0-py3.8.egg/wazuh_testing/qa_docs/output Output File |
Style guide
QA-docs executiontest_queue_socket_propertiesqa-docs --tests-path /home/mauro/Documents/Wazuh/issue/1850/wazuh-qa/tests/integration/test_analysisd/test_queue_socket_properties/ -t test_queue_socket_properties Results2022-01-18 15:38:22,322 - INFO - Looking for test_queue_socket_properties.py Output File |
As reported in the issue above, we need to check that the Analysisd's input socket (queue/sockets/queue) file remains after running Analysisd in test mode:
We can implement this test by checking that the following properties of the file won't change after running Analysisd in test mode:
Known versions where this test would fail
The text was updated successfully, but these errors were encountered: