Changes for page Test Speedup

Last modified by chrisby on 2025/03/08 11:39

From version 1.45

edited by chrisby
on 2024/05/05 17:57

Change comment: There is no comment for this version

To version 1.44

edited by chrisby
on 2024/05/05 17:55

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -24,6 +24,6 @@
  **Asynchronous Testing**
--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 comprehensively tested while you continue working without waiting. If the CI pipeline succeeds, the test suite has proven that your code is good. If the CI pipeline fails, you should get a notification like an SMS, email chat that triggers a ringing tone or desktop notification so that you immediately stop what you are doing to fix the problem. Push the fix again and continue working without waiting for the tests to finish.
++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 comprehensively tested while you continue working without waiting. If the CI pipeline succeeds, the test suite has proven that your code is good. If the CI pipeline fails, you should get a notification like an SMS or email that triggers a ringing tone so that you immediately stop what you are doing to fix the problem. Push the fix again and continue working without waiting for the tests to finish.
  It is not uncommon to have many CI pipelines running at the same time for the same developer. While this may require an advanced DevOps infrastructure, it is often worth the investment. Or you can simply use cloud providers that do this automatically in the background.