| ... |
... |
@@ -32,9 +32,9 @@ |
| 32 |
32 |
Every functionality you expect the software to provide at any moment. You should test: |
| 33 |
33 |
|
| 34 |
34 |
* **Functional Requirements** |
| 35 |
|
-** Use cases that are defined in project requirements. Tests are actually specification translated into code. |
| 36 |
|
-** Lower-level use cases derived from high-level project use cases 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. |
|
35 |
+** **High-level use cases** that are defined in project requirements. Tests are actually specification translated into code. |
| 37 |
37 |
* **Non-Functional Requirements** |
|
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, zeroes, negative numbers, empty lists, values with special meaning, exceptions, etc. |
| 39 |
39 |
** **Performance requirements** |
| 40 |
40 |
** **Security requirements** |
