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.32
edited by chrisby
on 2024/05/05 17:42
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, execute tests locally, wait for them to finish and if they pass then going on. To avoid long waiting times being unproductive, you only execute a few, very fast tests sacrificing that all tests check your latest changes. This is tolerable when working on yet isolated code and working with unit tests but as soon as integration with the rest of the code comes into play this becomes a problem. Either you execute only unit tests not taking advantage of the whole mightiness of your test suite or you run all tests and be unpro
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.