| ... |
... |
@@ -22,8 +22,7 @@ |
| 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 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. |
|
25 |
+** Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state. |
| 27 |
27 |
|
| 28 |
28 |
=== === |
| 29 |
29 |
|
