System Test - Wazuh DB (T0): The agent with state different than never_connected is added to a "Y" group by API

[damarisg]

Description

The aim here is to verify if the agent has a state other than never_connected and is added to a Y group by API tools. The nodes have registered the agent with group Y.

Test Details

Case 1:

Given a configured master
And two workers configured
And an agent connects to the master node
And the agent with state Active
And the agent is add to new group Y by API.
Then each node has the agent with its Y group after X seconds

Case 2:

Given a configured master
And two workers configured
And an agent connects to the master node
And the agent with state Disconnected
And the agent is add to new group Y by API.
Then each node has the agent with its Y group after X seconds

Case 3:

Given a configured master
And two workers configured
And an agent connects to the worker nodes
And the agent with state Active
And the agent is add to new group Y by API.
Then each node has the agent with its Y group after X seconds

Case 4:

Given a configured master
And two workers configured
And an agent connects to the worker nodes
And the agent with state Disconnected
And the agent is add to new group Y by API.
Then each node has the agent with its Y group after X seconds

Note:

• X: Estimated time for complete information synchronization, minimum 2*Z --- worker1 -> master -> worker1/2
• Z: Cluster synchronization period (default 10 seconds)

[CamiRomero]

These tests were applied on the 2506_system_test_assign_agent_to_a_group_api branch. The issue will be moved to the blocking state until the merge of core branch to master

[damarisg]

It was merged on qa-10771-agent-groups-files-to-wazuh-db branch and closed.