RL-70-mock-fake-user-story

[tom-rt]

Description

PLEASE MAKE SURE THAT THE BRANCH PR INCLUDES JIRA TICKET ID (for centreon-internal)

Please include a short resume of the changes and what is the purpose of PR. Any relevant information should be added to help:

• QA Team (Quality Assurance) with tests.
• reviewers to understand what are the stakes of the pull request.

Fixes # (issue)

Type of change

• [ ] Patch fixing an issue (non-breaking change)
• [ ] New functionality (non-breaking change)
• [ ] Breaking change (patch or feature) that might cause side effects breaking part of the Software

Target serie

• [ ] 21.04.x
• [ ] 21.10.x
• [ ] 22.04.x
• [ ] 22.10.x (master)

How this pull request can be tested ?

Please describe the procedure to verify that the goal of the PR is matched. Provide clear instructions so that it can be correctly tested.

Any relevant details of the configuration to perform the test should be added.

Checklist

Community contributors & Centreon team

• [ ] I have followed the coding style guidelines provided by Centreon
• [ ] I have commented my code, especially new classes, functions or any legacy code modified. (docblock)
• [ ] I have commented my code, especially hard-to-understand areas of the PR.
• [ ] I have rebased my development branch on the base branch (master, maintenance).

[sonarqube-decoration[bot]]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information