Test Cases Design for 4.3.7

[Mayons95]

This issue aims to track the effort for the analysis and design of the test cases for the new issues of the release 4.3.7.
Task to be perform:

• Analysis of PR on Review
• [:clock1: ] Infinite loop trying to check alerts index patterns after reinstalling Wazuh indexer #4293 - Pending definitive review
• Module settings are not persistent between updates #4179
• Wrong path for Wazuh logo customization #4337
• Type error filtering the CIS benchmark of a Windows agent #4347
• TypeError in the browser's developer console #4346
• Group report generation fails randomly #4348
• wazuh.yml in-file documentation #4349
• Short refresh timeout on manager restart #4181
• 4.3.5 unable to execute SQL Query for Windows CIS Benchmark View #4340
• [:clock1: ] Centralized service to restart Wazuh #4277 - Pending definitive review

[Mayons95]

Test cases for Wazuh Kibana App 4.3.7

4293 Infinite loop trying to check alerts index patterns after

reinstalling Wazuh indexer

Happy path steps:

Using a Wazuh stack deployment (Wazuh dashboard, Wazuh indexer, Wazuh server), configure and start de the components. The Wazuh indexer should be in an independent machine.
Access to Wazuh dashboard and navigate to Wazuh plugin, configure the API host to work as expected. Secure the index pattern related to Wazuh are created. Keep the browser tab in the Wazuh plugin.
Remove, reinstall and start the Wazuh indexer using the Wazuh install assistant following the next steps:

sudo bash wazuh-install.sh -u
sudo bash wazuh-install.sh --wazuh-indexer indexer
sudo bash wazuh-install.sh --start-cluster

Returns to the browser tab that has the Wazuh plugin and navigates to another plugin section. The plugin health check should run and it should finish each check successfully, then it should redirect to /overview plugin path and instantly should redirect to the /health-check path again.

#4359 Fix modules settings persistence between updates

Test

Manual

Same plugin version and revision, restart the plugin platform. The registry file should not be changed.
For different plugin versions or revisions, restart the plugin platform. The registry file should be rebuilt and keeps the host configuration.
Different plugin version or revision removes some extension of any host in the registry file, and restart the plugin platform. The registry file should be rebuilt and keeps the host configuration. The removed extension should be included in the host and have the default value.

###Automatic

A new test file was created. Run the test with:
in the plugin root directory: yarn test:jest server/start/initialize/index.test.ts

#4337 Wrong path for Wazuh logo customization

Given the user is in Wazuh Kibana App.
When the user navigate to Settings --> Configuration --> Logo Customization
Then on the Logo Customization section,  ‘/usr/share/wazuh-dashboard/plugins/wazuh/public/assets/’ url of the path is displayed.

#4346 TypeError in the browser's developer console

Given the user is in Wazuh Kibana App.
And The user opens the developer console of the dev tool on the browser
When the user navigates any modules outside Wazuh
And the user clicks the Home button
Then no error in the browser's developer console is displayed

#4350 Fixed errors in group reports

### Scenario: Error due to accessing a property of undefined

Given the user is in Wazuh Kibana App.
And Logged user in Management/Groups//Information, wait the time to the Wazuh API token expires.
When The user clicks on the "Export PDF" button.
Then The PDF should be generated without errors. Check the generated PDF.

### Scenario: Missing agents in the agent in the group table of group report.

Given the user is in Wazuh Kibana App.
And the group with more than 500 agents.
When The user clicks on the "Export PDF" button.
Then The PDF should be generated without errors and it should contain all the agents in the group displayed in a table.

#4181 Short refresh timeout on manager restart

Given the user is in Wazuh Kibana App
And the user navigates to Management --> Configuration
When the user selects the Edit Configuration link
Then the manager configuration XML file to edit is displayed
When the user finds and edits the vulnerability detector tag
And the user changes enable tag with No value
And the user selects the Save button
Then the manager configuration is saved
When the user selects the restart manager button
And the user confirms the restart manager
Then the wazuh app is restarted 
When the wazuh health check is running
Then all indicator of the health check is done

#4340 4.3.5 unable to execute SQL Query for Windows CIS Benchmark View

Given the user is in Wazuh Kibana App
And the user navigates to Modules  --> SCA
When the user selects the agent
Then the inventory tab is displayed
When the user writes on the filter or search field
Then the dropdown options are displayed 
And no error on the dropdown options is displayed

#4277 Centralized service to restart Wazuh

Scenario: Install from Cluster Mode.

Given the user is in Wazuh Kibana App
And the wazuh app was installed on cluster mode
And the user navigates to management->configuration
When the user selects the Edit Configuration link
Then the manager configuration XML file to edit is displayed
When the user finds and edits the vulnerability detector tag
And the user changes enable tag with No value
And the user selects the Save button
Then the manager configuration is saved
When the user selects the restart manager button
And the user confirms the restart manager
Then the wazuh app is restarted 
And no error message is displayed 
When the user navigates to management -> rules
Then the module section is displayed
And no health check is displayed

Scenario: Install from Manager Mode.

Given the user is in Wazuh Kibana App
And the wazuh app was installed on Manager mode
And the user navigates to management->configuration
When the user selects the Edit Configuration link
Then the manager configuration XML file to edit is displayed
When the user finds and edits the vulnerability detector tag
And the user changes enable tag with No value
And the user selects the Save button
Then the manager configuration is saved
When the user selects the restart manager button
And the user confirms the restart manager
Then the wazuh app is restarted 
And no error message is displayed 
When the user navigates to management -> rules
Then the module section is displayed
And no health check is displayed

#4349 wazuh.yml in-file documentation

Test Comment: This test is to check the documentation, so with one complete check it’s consider pass.

Access to: https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/config-file.html

This URL  should redirect you to the current version of Wazuh Documentation 
Settings should be displayed:
checks.metaFields
checks.timeFilter
checks.maxBuckets
extensions.hipaa
extensions.nist
extensions.tsc
extensions.oscap
extensions.gcp
This setting allows hiding Wazuh for the specified roles. Related issue: [wazuh/wazuh-kibana-app#3164](https://github.com/wazuh/wazuh-kibana-app/issues/3164)
disabled_roles
Name for the sample alerts index
alerts.sample.prefix
[cron](https://g.co/kgs/Mh1TYS) related settings: these settings configure the behavior of background tasks performed by the App.
cron.prefix
cron.statistics.status
cron.statistics.apis
cron.statistics.interval
cron.statistics.index.name
cron.statistics.index.creation
cron.statistics.shards
cron.statistics.replicas
These settings are used in the agents' enrollment interactive helper.
enrollment.dns
enrollment.password
Custom logos
customization.logo.app
customization.logo.sidebar
customization.logo.healthcheck
customization.logo.reports
Settings should not be displayed
wazuh-version.*: deprecated since 4.3.0. To be removed completely.
api.selector: deprecated. To be removed.
admin: seems to be no longer used. I assume it's been deprecated.
timeout: default value is set to 8000. Actual value is 20000.
wazuh.monitoring.shards: default value is set to 2. Actual value is 1.
wazuh.monitoring.creation: default value is d (daily). Actual value is w (weekly).

### Test cases for Wazuh Splunk 4.3.7

#1358 Broken suggestions in the API console

Given the user is in Wazuh Splunk App
And the user navigates to dev tools
And the user writes a part of a command (EX /get Agents)
And a list of suggestions should be displayed
And the user clicks a suggestion
Then the suggestion text is displayed on the query