Unit tests

[Fieldelm]

The customer looks for quality assurance and wants to see that your code is covered by unit tests. It is important to also cover negative scenarios, not only positive test cases.

• Every unit test method is well-arranged and follows the arrange-act-assert structure.

  • Unit test classes and methods adhere to the following naming conventions consistently.
    classes: Test
    methods: <expected input / tested state>
  • Every test class has at least one negative test case (or more, if it is plausible).
    • [ ]Code coverage of self-created business logic classes is above 90%.