Skip to Content

Changes for page Testing Principles

Last modified by chrisby on 2024/04/01 12:52
From version 5.11
edited by chrisby
on 2023/11/04 11:16
Change comment: There is no comment for this version
To version 5.12
edited by chrisby
on 2023/11/28 23:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,9 +4,9 @@
4 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 -* **Falsifiability** = The ability to fail.
7 +* **Falsifiability** = The ability to fail. Tests must be able to fail if the production code does not behave as expected.
8 8  ** 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.
9 -** Wrongfully passing tests lack the ability to fail properly and are hard to detect because everything seems fine, which is why it is so important to focus on preventing them. They do damage by appearing to validate functionality that they do not. A properly executed Test Driven Development workflow is one of the best ways to avoid these kinds of problems, which are described in [[this article>>doc:Software Engineering.Agile.Extreme Programming.Test-Driven Development.TDD Workflow Example.WebHome]].
9 +** Wrongfully passing tests lack the ability to fail properly and are hard to detect because everything seems fine, which is why it is so important to focus on preventing them. They do damage by appearing to validate functionality that they do not. A properly executed Test-Driven Development workflow is one of the best ways to avoid these kinds of problems, which are described in [[this article>>doc:Software Engineering.Agile.Extreme Programming.Test-Driven Development.TDD Workflow Example.WebHome]].
10 10  * **Determinism and Reproducibility**: Repeated tests should always produce the same result. The success of tests should never depend on anything other than the production code. Avoid sources of randomness that could cause the test to fail even though the production code is the same as it was when the tests passed in a previous test run. These include random number generators, threads, host-specific infrastructure (operating system, absolute paths, hardware: I/O speed or CPU load), networking over the local network or Internet (since the network or other hosts may sometimes be down), time/timestamps, pre-existing values in the database or files on the host system that are not in the source code.
11 11  * **Single Action Execution**: The entire setup and testing process execution should require a single click or shell command. Otherwise, they will not be used regularly, which reduces the quality assurance of the production code.
12 12  * **Independence**: Tests should be independent and not influenced by other tests; the order in which tests are executed should not matter.