Write unit-tests on a Test Client

[memorisecodead]

Workflow:

• Read about the integration testing of the server, read the documentation of the tests - Documentation.
• After investigation, write uni-tests on the Test Client - TestClient Note: Write unit-tests ONLY for public methods.
• Write tests for functionality, not write functionality for tests. Don't forget this.

  Criteria:

• The coverage of the test object must be less than 80%.
• Preservation of the current implementation of the test client, as well as operability.

[f1nal3]

I'd refrain from bothering with this since:

• It is not used in the statistics
• Will soon be reworked
• There is a reason test things are not considered during coverage report

[memorisecodead]

I'd refrain from bothering with this since:

• It is not used in the statistics
• Will soon be reworked
• There is a reason test things are not considered during coverage report

At this point, there are no tests for the current implementation. Regardless of the sonar, we stick to the rule written code - covered by tests. Even if there are changes to the test client in the future, the tests will be rewritten for the new implementation =)