| ... |
... |
@@ -8,7 +8,7 @@ |
| 8 |
8 |
=== General === |
| 9 |
9 |
|
| 10 |
10 |
* **Ultimate Goal** of testing: Reduce costs and increase productivity. Development with testing is faster and safer than without. |
| 11 |
|
-* **Definition 'Production Code':** Code that provides functionality to meet project requirements. |
|
11 |
+* **Definition 'Production Code':** Code that provides the functionalities of a system. |
| 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 |
=== === |
| ... |
... |
@@ -22,7 +22,8 @@ |
| 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 |
24 |
* **Documentation** |
| 25 |
|
-** Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state. |
|
25 |
+** Tests serve as the most up-to-date form of code documentation, capturing the expected behavior of the production code in its current state or of a third-party library. |
|
26 |
+** Good tests are quick and easy to understand because they are written in an expressive language that developers speak fluently. In addition, the actual documentation is often simply skipped over. |
| 26 |
26 |
|
| 27 |
27 |
=== === |
| 28 |
28 |
|
