Refactor Tests Files to new synchronization mechanism

[damarisg]

Due to the implementation of rsync as the new engine for FIM db synchronization the following tests need to be reworked to adapt to the new sync messages coming from rsync.

Test files

• test_max_eps_synchronization.py

The above test assesses the max sync events per second defined in syscheck configuration for the synchronization process.

[damarisg]

2022/03/16

Working with a new package, I ask Core Fim some weird behavior. I wait your answer.

2022/02/23

The test was launched and failed. Also, I tested manually, and the results were the same.
The current problem is that the created files are not synchronized, and the records of all the created files are not displayed. (File monitoring is lost.)

The Core Team is fixing some bugs that are related to these failures. So, It's blocked until solved.

2022/02/21

Note: Changes of each test refactored applied on new-synchronization-mechanism temp branch.

[Deblintrake09]

Update 2022/04/08

• Run tests on manager, Linux and Windows
• Fails on Windows and Linux
• Do manual testing
  Ask Core team for information https://wazuh-team.slack.com/archives/C019A838R6Y/p1649447731151189

Update 2022/04/11

• Manual testing on different fim Modes. It was found that the type of message is sent on realtime/whodata fim send_syscheck_event messages are sent, with type: event, and no synchro events are actually sent.
• Asked Core about results found, to continue with development.

Update 2022/04/13

• After Sync with team, it was decided to create two different tests, one for scheduled mode and one for realtime/whodata.
• Refactored test to work on scheduled mode, created file test_sync_max_eps_scheduled.py
• Working on refactor on test_sync_max_eps_rt_wd.py
• Messages not appearing on agent.

[Deblintrake09]

Update 2022/04/18 - 2022/04/20

• Debugged and fixed test
• Test fails on new package
• Core Team opened new Issue based on research done Fix maximun message per second in FIM DB synchronization wazuh#13189
• Move to blocked

[CamiRomero]

I am going to start working today on this Issue since they have been closed 12456 and 13189

[damarisg]

It was merged to 1915-fim-rsync-new-synchronization-mechanism branch.