| ... |
... |
@@ -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 |
|
| ... |
... |
@@ -32,7 +32,7 @@ |
| 32 |
32 |
Every functionality you expect the software to provide at any moment. You should test: |
| 33 |
33 |
|
| 34 |
34 |
* **Functional Requirements** |
| 35 |
|
-** **High-level use cases** that are defined in project requirements. Tests are actually specification translated into code. |
|
36 |
+** **High-level use cases** that are defined in project requirements by the customer. Tests are actually requirements translated into code. And customer requirements are usually translated into acceptance tests. |
| 36 |
36 |
* **Non-Functional Requirements** |
| 37 |
37 |
** **Lower-level use cases** derived from high-level project use cases that are not directly visible to end users, but form the backbone of software functionality. This includes the expected behavior of the underlying functions, classes, modules, and components. |
| 38 |
38 |
** **Border cases** that could theoretically occur, such as maximum/minimum values, nulls, invalid input outside the permissible value range, zeroes, negative numbers, empty lists, values with special meaning, exceptions, etc. |
