Changes for page Test Speedup
Last modified by chrisby on 2025/03/08 11:39
Summary
-
Page properties (1 modified, 0 added, 0 removed)
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 doing and fix the problem.Pushthe fix againand 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 changes are okay. If the CI pipeline fails, you should receive a notification, such as an SMS, email, or chat message that triggers a ringtone, or a desktop notification, so you can immediately stop what you are working on and fix the problem first. Apply the fix and continue working without waiting for the tests to finish. 28 28 29 -It is not uncommon t ohave 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.29 +It is not uncommon that one developer triggers 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.