| ... |
... |
@@ -2,11 +2,12 @@ |
| 2 |
2 |
* **Definition 'Production Code':** Represents the actual software functionality designed to fulfill project requirements. |
| 3 |
3 |
* **Definition 'Test Code':** Often referred to as "tests," is written to verify the functionality of production code. |
| 4 |
4 |
|
|
5 |
+ |
| 5 |
5 |
=== Benefits of Testing === |
| 6 |
6 |
|
| 7 |
7 |
* **Quality Assurance** |
| 8 |
8 |
** **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. |
| 9 |
|
-** **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. |
|
10 |
+** **Early Feedback**: Writing tests and refactoring code increases productivity by providing immediate error feedback. This is especially true for catching accidental bugs caused by code changes. The earlier bugs are caught, the cheaper they are to fix. |
| 10 |
10 |
** **Bug Location Detection**: Tests identify bug locations, saving debugging time. |
| 11 |
11 |
* **Testable Design** |
| 12 |
12 |
** 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. |
