Skip to Content

Changes for page Test-Driven Development

Last modified by chrisby on 2024/08/27 08:42
From version 1.28
edited by chrisby
on 2023/12/29 21:24
Change comment: There is no comment for this version
To version 1.29
edited by chrisby
on 2024/01/13 18:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -27,3 +27,14 @@
27 27  * **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.
28 28  * **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.
29 29  * **Technical Metric**: TDD is a technical agile practice, and therefore code coverage is a metric for developers to make decisions about, not the business.
30 +
31 +### Red-Green-Refactor (RGB)
32 +
33 +This is a simple model that describes the iterative TDD and refactoring workflow:
34 +
35 +1. Write a test that initially fails. (red terminal output)
36 +1. Implement production code to pass the test. (green terminal output)
37 +1. Refactor and make sure the tests still pass.
38 +1. Repeat until done.
39 +
40 +A more complex workflow that includes TDD and versioning with git can be found [[here|path:/bin/view/Software%20Engineering/Agile/Extreme%20Programming/Test-Driven%20Development/TDD%20Workflow%20Example/]].