Changes for page Test Speedup

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,8 +1,7 @@
1	1	Fast testing not only saves time, but also enables more frequent execution, leading to improved code quality. Optimizing the speed of test execution is therefore critical. While extensive and frequent testing is ideal, it shouldn't excessively slow the pace of development.
2	2
3		-### Measures
	3	+### General Measures
4	4
5		-* **Test type segregation**: Unit tests tend to run much faster than other types of tests. For large test suites, you should consider running unit tests regularly on the developer's local machine, while scheduling more resource-intensive tests in a CI environment. The CI environment can, for example, run the slower tests in parallel and notify you just in case something fails. If the tests take too long for this approach, you can run them at a fixed rate, usually once a day at midnight. Also see [[Types of Tests|doc:Software Engineering.Testing.Types of Tests.WebHome]].
6	6	* **Selective Testing**: You don't need to run all tests every time. It can be sufficient to run only the tests related to recently changed code, or only the fast tests, and then run all the tests when you finished a major implementation step.
7	7	* **Mock slow dependencies** to minimize code execution time, especially operations such as I/O, transaction management, and networking.
8	8	* **Prefer in-memory databases during testing** for cleaner and faster operations compared to standard databases.
...	...	@@ -10,20 +10,16 @@
10	10	* If execution time remains constant, CPU is the bottleneck. Mitigate with faster CPUs, more cores, or additional machines.
11	11	* If execution time decreases, I/O is the bottleneck. Use more threads, faster storage (such as SSDs), or additional storage for concurrent filesystem operations.
12	12	* **Improve I/O speed by using RAM disks**, such as Linux's tmpfs tool. Configure your tests to direct all file interactions to the RAM disk.
13		-* **Parallelize test execution.** Multiple threads can improve execution speed even on single-core processors by keeping the CPU busy while other threads wait for disk I/O.
14		-* **Offload CPU-intensive tasks** to cloud-based computing resources using automation scripts:
15		- * Upload project files to the cloud.
16		- * The cloud service builds the project, runs tests, and generates a test report.
17		- * Upon completion, download the test report from the cloud.
	12	+* **Parallelize test execution.** Multiple threads can improve execution speed even on single-core processors by keeping the CPU busy while other threads wait for disk
18	18
19		-### Asynchronous Testing
	14	+### Use DevOps Infrastructure
20	20
21		-**Synchronous Testing**
	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.
22	22
23		-A simple TDD workflow is to write new code, run tests locally, wait for them to finish, and if they pass, move on. To avoid long wait times, you run only a few very fast tests. This is fine when you are working on isolated code that is checked by unit tests, but as soon as integration of the new code with the old code comes into play, it becomes a problem. Now you have two bad choices: Either you run a few fast tests and do not use the full power of your test suite, resulting in low coverage and not detecting possible bugs that would have been easier to fix if they had been detected earlier, or you run all the tests locally and are unproductive for a long time while waiting for them to finish. This problem can be solved with asynchronous testing.
24		-
25		-**Asynchronous Testing**
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, 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		-
29		-It is not uncommon for a single developer to trigger many CI pipelines running simultaneously. While this technique may require advanced DevOps infrastructure to implement, it's often worth the investment to set it up. Or you can simply pay cloud providers like GitLab or GitHub to use their infrastructure, which provides this capability.
	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.
	20	+ * **CI Concurrency**: Drastically enhance test execution speed by enabling concurrent CI pipelines and jobs.
	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	+ * **Concurrent CI jobs**: Split the test suite into multiple independently executable CI jobs to allow concurrent execution.
	23	+ * Both of these measures require multiple machines to run the jobs, which can be demanding on the DevOps infrastructure but is often worth the cost.
	24	+ * **Scheduled Testing**: A less resource-intensive alternative is to run large test suites at a fixed interval, typically once a day at midnight, and run only the fast or important tests locally.