Skip to Content

Changes for page Tips and Tricks

Last modified by chrisby on 2024/04/01 13:11
From version 1.11
edited by chrisby
on 2023/05/29 16:45
Change comment: There is no comment for this version
To version 1.12
edited by chrisby
on 2023/05/29 16:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -51,8 +51,8 @@
51 51  assertTrue(y);
52 52  {{/code}}
53 53  
54 -* If certain production code needs to be called several times with slightly different arguments, it may be useful to iterate over a list of these arguments, calling the production code and then asserting the result on each iteration. It is then often good practice to print out each element before each assertion. If an element causes a test to fail, the terminal output will immediately show which element caused the error.
55 -* If you find a bug or a case that has not yet been tested, it is your duty to create a test that covers it, so that the software is stable against that problem from that moment on.
56 -* Inaccurate results should never be asserted against an exact value, but only within an expected range of approximation. This includes all floating-point numbers, which are always imprecise.
57 -* Don't exclusively test third-party code, such as other services or libraries. It's not your job, and it's probably a duplication of effort. Only test if it works correctly with your own code.
58 -* It would be very cumbersome to perform input validations, such as the famous null checks, and corresponding tests for each unit. A common solution is to define a module consisting of several classes. The class at the top, which receives the input for the first time, validates it once. All subsequent classes can safely assume that the input is not null when processing it, and no longer need to explicitly check it.
54 +* **Test Case Logging**: If certain production code needs to be called several times with slightly different arguments, it may be useful to iterate over a list of these arguments, calling the production code and then asserting the result on each iteration. It is then often good practice to print out each element before each assertion. If an element causes a test to fail, the terminal output will immediately show which element caused the error.
55 +* **Bug Coverage Responsibility**: If you find a bug or a case that has not yet been tested, it is your duty to create a test that covers it, so that the software is stable against that problem from that moment on.
56 +* **Range-Based Assertions**: Inaccurate results should never be asserted against an exact value, but only within an expected range of approximation. This includes all floating-point numbers, which are always imprecise.
57 +* **Focus on Own Code**: Don't exclusively test third-party code, such as other services or libraries. It's not your job, and it's probably a duplication of effort. Only test if it works correctly with your own code.
58 +* **Avoid Cascading Validation**: It would be very cumbersome to perform input validations, such as the famous null checks, and corresponding tests for each unit. A common solution is to define a module consisting of several classes. The class at the top, which receives the input for the first time, validates it once. All subsequent classes can safely assume that the input is not null when processing it, and no longer need to explicitly check or write tests for such cases.