| ... |
... |
@@ -1,9 +1,9 @@ |
| 1 |
1 |
=== Foreword === |
| 2 |
2 |
|
| 3 |
3 |
(% style="text-align: justify;" %) |
| 4 |
|
-The chapters presented here are a concise summary of more theoretical and high-level knowledge. It is recommended that you are familiar with writing very basic tests and mocks, and understand the concepts of polymorphism and [[dependency injection>>doc:Software Architecture.Dependency Injection.WebHome]] before reading on. |
|
4 |
+The chapters presented here are a concise summary of more theoretical and high-level knowledge. It is recommended that you are familiar with writing very basic tests and mocks, and understand the concepts of polymorphism and [[dependency injection>>doc:Software Engineering.Dependency Injection.WebHome]] before reading on. |
| 5 |
5 |
|
| 6 |
|
-=== === |
|
6 |
+=== === |
| 7 |
7 |
|
| 8 |
8 |
=== General === |
| 9 |
9 |
|
| ... |
... |
@@ -11,13 +11,13 @@ |
| 11 |
11 |
* **Definition 'Production Code':** Code that provides functionality to meet project requirements. |
| 12 |
12 |
* **Definition 'Test Code':** Often referred to as "tests", it is written to verify the correct functionality of the production code. |
| 13 |
13 |
|
| 14 |
|
-=== === |
|
14 |
+=== === |
| 15 |
15 |
|
| 16 |
16 |
=== Benefits of Testing === |
| 17 |
17 |
|
| 18 |
18 |
* **Quality Assurance** |
| 19 |
19 |
** **Automated Testing**: Minimizes the need for human source code checking or manual testing, providing a cost-effective way to ensure continuous quality assurance and the correct functioning of software at all times. |
| 20 |
|
-** **Early Feedback**: Tests provide immediate bug feedback. This is especially true for detecting accidentally introduced bugs caused by code changes. The earlier bugs are detected, the cheaper they are to fix. |
|
20 |
+** **Early Feedback**: Tests provide immediate bug feedback. This is especially true for detecting accidentally introduced bugs caused by code changes. The earlier bugs are detected, the cheaper they are to fix. This also eliminates the fear of introducing bugs when writing or modifying code. |
| 21 |
21 |
** **Bug Location Detection**: Tests identify bug locations, saving debugging time. |
| 22 |
22 |
* **Testable Design** |
| 23 |
23 |
** Writing tests automatically enforces design best practices, resulting in a 'testable design' and higher quality code. Good code and architecture are testable, and vice versa. |
| ... |
... |
@@ -24,7 +24,7 @@ |
| 24 |
24 |
* **Documentation** |
| 25 |
25 |
** Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state. |
| 26 |
26 |
|
| 27 |
|
-=== === |
|
27 |
+=== === |
| 28 |
28 |
|
| 29 |
29 |
=== What should be tested? === |
| 30 |
30 |
|
