Skip to Content

Changes for page Test Speedup

Last modified by chrisby on 2025/03/08 11:39
From version 1.59
edited by chrisby
on 2024/06/07 11:43
Change comment: There is no comment for this version
To version 1.60
edited by chrisby
on 2024/08/27 08:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,7 @@
16 16  A good developer should learn modern DevOps concepts, especially CI/CD pipelines and jobs. Beginners may want to start with a third-party DevOps infrastructure provider, such as GitLab or GitHub.
17 17  
18 18  * **Test type segregation**: Regularly run fast tests, such as unit tests, on the developer's local machine, while scheduling more resource-intensive tests in a CI environment.
19 -* **Asynchronous Testing**: Running the entire test suite locally results in long wait times that block development. Instead, push the code to the source repository and let the CI environment run the test suite while you continue development. If a CI job fails, you will be notified so that you can prioritize fixing the problem.
19 +* **Asynchronous Testing**: Running the entire test suite locally may result in long wait times that block development. Instead, push the code to the source repository and let the CI environment run the test suite while you continue development. If a CI job fails, you will be notified so that you can prioritize fixing the problem.
20 20   * **CI Concurrency**: Drastically enhance test execution speed by enabling concurrent CI pipelines and jobs.
21 21   * **Concurrent CI pipelines**: Allow the developer to push code and spawn new CI pipelines immediately on different machines, even if previous pipelines are still running.
22 22   * **Concurrent CI jobs**: Split the test suite into multiple independently executable CI jobs to allow concurrent execution.