Skip to Content

Changes for page Testing Principles

Last modified by chrisby on 2024/04/01 12:52
From version 2.5
edited by chrisby
on 2023/05/30 17:40
Change comment: There is no comment for this version
To version 2.6
edited by chrisby
on 2023/05/30 17:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,8 @@
1 1  * **Code Coverage**:
2 2  ** Definition: The percentage of classes/methods/lines of code executed during testing. There is class coverage, method coverage and line coverage. Code coverage is generally a useful quality metric and indicator of missing tests, but it is not a guarantee of good tests or that all relevant cases are covered, so take it with a grain of salt.
3 -** **100% code coverage** is the goal. Untested code is insecure code and prone to bugs.
3 +** Aim for **100% code coverage**. Untested code is risky and bug-prone. Although it's rarely exactly achieved, it's a worthy goal that encourages thorough testing.
4 +** **Meaningful Tests:** Don't add tests that don't add value, e.g. to just reach the 100% coverage, or test something that has already been tested.
4 4  ** Leverage **code coverage tools** that determine code coverage during test execution.
5 -** **Meaningful Tests:** Don't add tests that don't add value or test something that has already been tested.
6 -
7 7  * **Failure Strictness**: If at least one test fails, it requires the developer's attention. He is not allowed to proceed with other work until that problem is fixed, and all tests must pass without exception.
8 8  * **Falsifiability** = The ability to fail.
9 9  ** Wrongfully failing tests are easy to detect, because a good developer will pay attention to all failing tests and fix the problems before moving on.