| ... |
... |
@@ -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 |
|
| ... |
... |
@@ -24,9 +24,9 @@ |
| 24 |
24 |
Every functionality you expect the software to provide at any moment. You should test: |
| 25 |
25 |
|
| 26 |
26 |
* **Functional Requirements** |
| 27 |
|
-** **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. |
|
28 |
+** **High-level business use cases** defined by the customer in project requirements. Tests are essentially requirements translated into code. And customer requirements are typically translated into acceptance tests. |
| 28 |
28 |
* **Non-Functional Requirements** |
| 29 |
|
-** **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. |
|
30 |
+** **Lower-level technical use cases** derived from high-level business 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 components, modules and units. |
| 30 |
30 |
** **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. |
| 31 |
31 |
** **Performance requirements** |
| 32 |
32 |
** **Security requirements** |
