Skip to Content

Changes for page Test Speedup

Last modified by chrisby on 2025/03/08 11:39
From version 1.26
edited by chrisby
on 2024/05/05 17:35
Change comment: There is no comment for this version
To version 1.21
edited by chrisby
on 2024/05/05 17:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,12 +18,6 @@
18 18  
19 19  ### Asynchronous Testing
20 20  
21 -**Synchronous Testing**
21 +Writing new code, executing local tests, waiting for them to finish if they pass going on, is a workflow that works well when the test take a few seconds only. This means this flow is limited to the execution of very fast and sometimes few tests.
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. You have to accept one of the two advantages then:
24 -
25 -**Asynchronous Testing**
26 -
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 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.
23 +* 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.