Changes for page Test Speedup

Last modified by chrisby on 2025/03/08 11:39

From version 1.33

edited by chrisby
on 2024/05/05 17:43

Change comment: There is no comment for this version

To version 1.35

edited by chrisby
on 2024/05/05 17:45

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -20,7 +20,7 @@
  **Synchronous Testing**
--A simple TDD workflow is to write new code, run tests locally, wait for them to finish, and if they pass, move on. To avoid long waiting times being unproductive, you run only a few very fast tests, sacrificing the fact that all tests check your latest changes. This is tolerable when you are working on isolated code and using unit tests, but as soon as integration with the rest of the code comes into play, it becomes a problem. Either you run only unit tests and do not take advantage of the full power of your test suite, or you run all tests and are unproductive for a long time while waiting for them to finish. This problem can be solved with asynchronous testing.
++A simple TDD workflow is to write new code, run tests locally, wait for them to finish, and if they pass, move on. To avoid long wait times, you run only a few very fast tests. This is tolerable when you are working on isolated code and using unit tests, but as soon as integration of the new code with the old code comes into play, it becomes a problem. You have two bad choices: either you run only a few fast tests and do not use the full power of your test suite, possibly missing bugs that would be easier to fix if they were caught earlier, or you run all the tests locally and are unproductive for a long time while waiting for them to finish. This problem can be solved with asynchronous testing.
  **Asynchronous Testing**