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 - isa workflowthatworks wellwhenthe test take afewseconds only.Thishasthe disadvantage thatyouonlycheckyour codechanges forcorrectnessagainstjust a few veryfasttests.27 +You should have DevOps infrastructure which when pushing code to the code repository triggers a CI pipeline executing all tests. Doing that enables you to directly go on working without the need to wait minutes for the tests to finish. If the CI pipeline succeeds, the comprehensive test suite proofed your code to be fine. 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 -I nsteadof waiting for your teststo finish locally,youshould have a DevOps infrastructure which triggersa CI pipeline when pushing the code executingalltests. Doing thatenables you to directly go on working without the need to waitminutes for the tests to finish. In case the CI pipeline fails,youshould get a notification to fix theCI pipeline immediately. This enables quite comprehensive testing, even having the same testing jobs running in parallel, even long taking ones.29 +It is not unusual that many CI pipel