Skip to Content

Changes for page Test Speedup

Last modified by chrisby on 2025/03/08 11:39
From version 1.37
edited by chrisby
on 2024/05/05 17:47
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,8 +20,10 @@
20 20  
21 21  **Synchronous Testing**
22 22  
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.
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 25  **Asynchronous Testing**
26 26  
27 -You should have DevOps infrastructure which when pushing code to the code repository triggers a CI pipeline executing all tests. Doing that enables you to directly go on working without the need to wait minutes for the tests to finish. If the CI pipeline succeeds, the comprehensive test suite proofed your code to be fine. If the CI pipeline fails, you should get a notification like an SMS or Email, abort your current work immediately to fix the CI pipeline immediately. This enables quite comprehensive testing, even having the same testing jobs running in parallel, even long taking ones.
27 +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.
28 +
29 +Instead of waiting for your tests to finish locally, you should have a DevOps infrastructure which triggers a CI pipeline when pushing the code executing all tests. Doing that enables you to directly go on working without the need to wait minutes for the tests to finish. In case the CI pipeline fails, you should get a notification to fix the CI pipeline immediately. This enables quite comprehensive testing, even having the same testing jobs running in parallel, even long taking ones.