You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: doc/main/intro/testing_approach.rst
+3-3
Original file line number
Diff line number
Diff line change
@@ -11,19 +11,19 @@ There are four main types of errors/hazards you can encounter in the development
11
11
* Race conditions and deadlocks
12
12
13
13
|short_name| testing approach is designed to provide high coverage of these error types.
14
-
All types of errors are covered with unit testing and review.
14
+
All types of errors are covered with unit testing and code review.
15
15
16
16
Code coverage metrics are tracked to ensure high code coverage with tests. Uncovered branches are analyzed manually.
17
17
Memory errors and data races are additionally covered by special tools that include thread and memory sanitizers.
18
18
19
19
Race conditions and deadlocks are the most complicated errors.
20
20
They are covered by:
21
21
22
-
* **Unit tests** that, however, have limited capability to catch such errors
22
+
* **Unit tests** that, however, have limited capability to catch such errors.
23
23
* **Integration tests**. Multiple different functionalities are heavily combined to emulate user use cases that may trigger such errors based on prior knowledge and expertise.
24
24
* **Stress testing with different possible combinations**. It ensures that even rarely triggered error conditions are caught by testing.
25
25
26
-
.. note:: Every fix is required to be covered by a test to guarantee the detection of such issues in the future.
26
+
.. note:: Every fix is required to be covered by a regression test to guarantee the detection of such issues in the future.
27
27
28
28
Continuous Integration triggers all the tests on each commit. This ensures that:
0 commit comments