| ... |
... |
@@ -15,8 +15,9 @@ |
| 15 |
15 |
* **Testable Design** |
| 16 |
16 |
** 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. |
| 17 |
17 |
* **Documentation** |
| 18 |
|
-** 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. |
| 19 |
|
-** 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. |
|
18 |
+** **Always Up To Date**: 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. |
|
19 |
+** **Code Is Best Documentation**: 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. |
|
20 |
+** **Behavior Is Easier Than Implementation**: Tests are a clearer representation of behavior than the implementation itself. Tests specify the input for a given code and assert the expected output, providing an intuitive understanding that's easier to grasp than the intricacies of production code. Simply put, what code does is easier to understand than how it does it. |
| 20 |
20 |
|
| 21 |
21 |
=== What should be tested? === |
| 22 |
22 |
|
