Skip to Content

Changes for page Test-Driven Development

Last modified by chrisby on 2024/08/27 08:42
From version 1.24
edited by chrisby
on 2023/12/02 19:17
Change comment: There is no comment for this version
To version 1.25
edited by chrisby
on 2023/12/08 07:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,7 @@
16 16  
17 17  **Remarks**
18 18  
19 -* **Not compiling is a failure**: For example, if the test code requires a function from the production code that has not yet been defined, compilation will fail.
19 +* **Not compiling is a failure**: For example, if the test code requires a function from the production code that has not yet been defined, compilation will fail. Since the test fails, you must next go to the production code and make the test pass.
20 20  * **Workflow**: In practice, you start writing a test until it fails, then switch to production until it passes, switch back to test code until it fails, and so on until the feature is complete. This leads to a very fast oscillation of switching between test code and production code. The last test should have passed within the last few minutes.
21 21  * **Debugging**: The very short TDD cycles result in far fewer bugs. Bugs may still occur, but they are often trivial and don't require debugging. Experienced developers are capable of debugging, but they do not spend much time on it because of the consistent use of TDD.
22 22  * **The tests need to run fast** so as not to block the developer from doing his task. See this [[test execution speed enhancing article|doc:Software Engineering.Testing.Enhance Test Execution Speed.WebHome]].