Skip to Content

Changes for page Testing

Last modified by chrisby on 2024/06/20 14:42
From version 4.8
edited by chrisby
on 2023/10/27 09:11
Change comment: There is no comment for this version
To version 4.10
edited by chrisby
on 2023/11/04 11:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,7 +13,7 @@
13 13  ** **Early Feedback**: Tests provide immediate bug feedback. This is especially true for detecting accidentally introduced bugs caused by code changes. The earlier bugs are detected, the cheaper they are to fix. This also eliminates the fear of introducing bugs when writing or modifying code.
14 14  ** **Bug Location Detection**: Tests identify bug locations, saving debugging time.
15 15  * **Testable Design**
16 -** Writing tests automatically enforces design best practices, resulting in a 'testable design' and higher quality code. Good code and architecture are testable, and vice versa.
16 +** Writing tests automatically forces developers to apply specific design best practices, resulting in a [[testable design>>doc:.Testable Design.WebHome]] that improves code and architecture testability, an important quality criterion.
17 17  * **Documentation**
18 18  ** **Always Up To Date**: Tests serve as the most up-to-date form of code documentation, capturing the expected behavior of the production code in its current state or of a third-party library.
19 19  ** **Code Is Best Documentation**: Good tests are quick and easy to understand because they are written in an expressive language that developers speak fluently. In addition, the actual documentation is often simply skipped over.