Changes for page Test-Driven Development

Last modified by chrisby on 2024/08/27 08:42

From version 2.1

edited by chrisby
on 2024/03/04 21:48

Change comment: Renamed back-links.

To version 1.29

edited by chrisby
on 2024/01/13 18:25

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -20,7 +20,7 @@
  * **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. Run tests on the code you are working on at least every few minutes.
      * Side note: Run all tests in the test suite at least once a day.
  * **Debugging**: The very short TDD cycles result in much less time spent debugging. Bugs still occur, but they are contained in the last incrementally changed small snippet of code, making them trivial to find and fix. Experienced developers are capable of debugging, but they do not spend much time on it because of the consistent use of TDD.
--* **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.Test Speedup.WebHome]].
++* **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]].
  ### Code Coverage