Skip to Content

Changes for page Test Speedup

Last modified by chrisby on 2025/03/08 11:39
From version 1.28
edited by chrisby
on 2024/05/05 17:37
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

Details

Page properties
Content
... ... @@ -20,10 +20,8 @@
20 20  
21 21  **Synchronous Testing**
22 22  
23 -A simple test-driven workflow is to write new code, execute tests locally, wait for them to finish and if they pass then going on. To avoid long wYou only execute a few, very fast tests sacrificing that all tests check your latest changes.
23 +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.
24 24  
25 -Although asynchronous testing has its place when
26 -
27 27  **Asynchronous Testing**
28 28  
29 29  is a workflow that works well when the test take a few seconds only. This has the disadvantage that you only check your code changes for correctness against just a few very fast tests.