Skip to Content

Changes for page Test-Driven Development

Last modified by chrisby on 2024/08/27 08:42
From version 2.3
edited by chrisby
on 2024/04/13 13:56
Change comment: There is no comment for this version
To version 2.5
edited by chrisby
on 2024/08/27 08:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -25,9 +25,9 @@
25 25  
26 26  * **Incomplete Validation**: Passing tests doesn't mean that everything works, just that the tested parts aren't broken. Code coverage is a good first indicator of whether there are enough tests.
27 27  * **Almost 100% Code Coverage**: Code coverage needs to be high, ideally 100%, but in reality the practical achievable is in the high 90s. But code coverage alone is no guarantee of useful tests, so it should be taken with a grain of salt. It is better to look at the tests to get an idea of the actual quality of the test suite.
28 -* **Technical Metric**: TDD is a technical agile practice, and therefore code coverage is a metric for developers to make decisions about, not the business.
28 +* **Technical Metric**: TDD is a <ins>technical</ins> agile practice, and therefore code coverage is a metric for developers to make decisions about, not the business.
29 29  
30 -### Red-Green-Refactor (RGB)
30 +### Red-Green-Refactor
31 31  
32 32  This is a simple model that describes the iterative TDD and refactoring workflow:
33 33