Skip to Content

Changes for page Test Speedup

Last modified by chrisby on 2025/03/08 11:39
From version 1.49
edited by chrisby
on 2024/05/05 18:01
Change comment: There is no comment for this version
To version 1.48
edited by chrisby
on 2024/05/05 18:00
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 you push code into the code repository, there should be a DevOps infrastructure that triggers a CI pipeline that runs all the tests. This allows your code to be extensively tested while you continue to work without waiting. If the CI pipeline succeeds, the test suite has proven that your code changes are okay. If the CI pipeline fails, you should receive a notification, such as an SMS, email, or chat message that triggers a ring tone, or a desktop notification, so you can immediately stop what you are doing and fix the problem. Push the fix again and continue working without waiting for the tests to finish.
27 +When you push code into the code repository, there should be a DevOps infrastructure that triggers a CI pipeline that runs all the tests. This allows your code to be extensively tested while you continue to work without waiting. If the CI pipeline succeeds, the test suite has proven that your code is okay. If the CI pipeline fails, you should receive a notification, such as an SMS, an email chat that triggers a ringtone, or a desktop notification, so that you can immediately stop what you are doing and fix the problem. Push the fix again and continue working without waiting for the tests to finish.
28 28  
29 29  It is not uncommon to have many CI pipelines running simultaneously for the same developer. While this may require advanced DevOps infrastructure, it's often worth the investment. Or you can simply use cloud providers that do this automatically in the background.