Skip to Content

Changes for page Test Speedup

Last modified by chrisby on 2025/03/08 11:39
From version 1.43
edited by chrisby
on 2024/05/05 17:54
Change comment: There is no comment for this version
To version 1.24
edited by chrisby
on 2024/05/05 17:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,12 +18,12 @@
18 18  
19 19  ### Asynchronous Testing
20 20  
21 -**Synchronous Testing**
21 +The Problem
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 fine when you are working on isolated code which is checked by unit tests, but as soon as integration of the new code with the old code comes into play, it becomes a problem. Now, 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 test-driven workflow is to write new code, execute tests locally, wait for them to finish and if they pass then going on.
24 24  
25 -**Asynchronous Testing**
25 +The Solution
26 26  
27 -when pushing code to the code repository there should be DevOps infrastructure that triggers a CI pipeline executing all tests. Doing that enables you to get your code comprehensively tested while you can directly go on working without the need to wait. If the CI pipeline succeeds, the test suite proofed your code to be fine. If the CI pipeline fails, you should get a notification like an SMS or Email which triggers a ringing tone, so that you abort your current work immediately to fix the problem. Push the fix again and continue working without waiting for any tests to finish.
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 28  
29 -It is not unusual that many CI pipelines run at the same time for the same developer. Although this may pose an advanced DevOps infrastructure it is often worth the investment. Or you simply use cloud providers automatically taking care of that in the background.
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 piepline 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.