| ... |
... |
@@ -31,6 +31,8 @@ |
| 31 |
31 |
** **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. |
| 32 |
32 |
** **Performance requirements** |
| 33 |
33 |
** **Security requirements** |
|
34 |
+** **Load requirements**, when software is expected to handle a certain number of requests per second. |
|
35 |
+* In general, you should always test **happy path** requirements, where everything works as expected, and **unhappy path** requirements, where something goes wrong or an unusual input is provided. Writing tests for the latter makes the software robust against misuse. |
| 34 |
34 |
|
| 35 |
35 |
=== Related Topics === |
| 36 |
36 |
|
