Closed Mayons95 closed 2 years ago
Test | Chrome | Safari | Firefox | Package |
---|---|---|---|---|
External-Documentation-Links | π’ | β« | π’ | 8.1.4 |
Fix API console to allow payloads in requests | π’ | β« | π’ | 8.1.4 |
Management - logs | π’ | β« | π’ | 8.1.4 |
Test | Chrome | Safari | Firefox | Package |
---|---|---|---|---|
External-Documentation-Links | π’ | β« | π’ | 8.1.7 |
Fix API console to allow payloads in requests | π’ | β« | π’ | 8.1.7 |
Management - logs | π’ | β« | π’ | 8.1.7 |
Test | Chrome | Safari | Firefox | Package |
---|---|---|---|---|
External-Documentation-Links | π’ | β« | π’ | 8.1.10 |
Fix API console to allow payloads in requests | π’ | β« | π’ | 8.1.10 |
Management - logs | π’ | β« | π’ | 8.1.10 |
Test | Chrome | Safari | Firefox | Package |
---|---|---|---|---|
External-Documentation-Links | π’ | β« | π’ | 8.2.6 |
Fix API console to allow payloads in requests | π’ | β« | π’ | 8.2.6 |
Management - logs | π’ | β« | π’ | 8.2.6 |
All tests have passed
Wazuh v4.3.6
Status legend: β« - None π΄ - Rejected π’ - Approved
In the case of π΄, create and link the issue.
Scenarios to test:
1) Install the Wazuh app on Splunk 2) Set the connection to Wazuh API 3) Set the configuration to Wazuh Forwarder 4) Check that the charts are displayed.
Test cases for Wazuh Splunk App 4.3.6
@External-Documentation-Links
Fix Links to Wazuh Documentation #1351 Scenario: Documentation links redirect to Wazuh documentation Given The Wazuh admin user is logged When The user navigates to Configuration/Registration service And The user clicks on the βHow to use the registration serviceβ option Then The user should be redirected to the Wazuh documentation. And the section of the documentation should match the Wazuh section name where the user was.
Fix API console to allow payloads in requests #1296
Test comments: On the linked PR there are more path to check the documentation links.
Test 1: common use Test that any available API endpoint works properly. The followings requests can be used:
GET /security/users/
POST /security/users/ { "username": "user_test", "password": "Pa$$word123" }
PUT /security/users/100/ { "password": "pa$$word" }
PUT /security/users/100/ { "password": "A$61a78e492" }
DELETE /security/users?user_ids=100
GET /agents/999/key GET /bsdg GET /syscollector/000/packages?search=ssh&limit=1
GET /mitre/techniques
GET /agents/ { "invalid": "query param" } Test 2: edge cases Test that unexpected errors are handled properly, for example, when a timeout happens.
The GET /mitre/techniques timeouts every time on a fresh environment. To force this behavior, reduce the App's timeout setting, then down any manager node (Docker), and rebuild it, so its cache is cleared. Finally go to the API console and launch the request.
@Logs
Management log section#1354 Scenario: Reallow demon processors Given The Wazuh admin user is logged When The user navigates to management/logs And The user clicks on the log selector And The user should be able to see task-manager and agent-upgrade on the log list And The user selects any of these logs Then The user could see log entries for the selected log