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.41
edited by chrisby
on 2024/05/05 17:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,6 +24,6 @@
24 24  
25 25  **Asynchronous Testing**
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 +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 and . If the CI pipeline fails, you should get a notification like an SMS or Email, abort your current work immediately to fix the problem. Push the fix again and continue working without waiting for any tests to finish.
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 +It is not unusual that many CI pipelines run at the same time for the same developer. Although this poses a quite huge