Skip to Content

Changes for page Testing Principles

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

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
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 3  ** Aim for **100% code coverage**. Untested code is risky and bug-prone. Although 100% is 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 +** **Meaningful Tests: **Only add tests that add value, e.g. don't add tests just to achieve 100% code coverage or to test something that has already been tested.
5 5  ** Leverage **code coverage tools** that determine code coverage during test execution.
6 6  * **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.
7 7  * **Falsifiability** = The ability to fail.