| ... |
... |
@@ -22,8 +22,8 @@ |
| 22 |
22 |
(% style="text-align: justify;" %) |
| 23 |
23 |
Every functionality you expect the software to provide at any moment. Depending on the overall requirements, you should test: |
| 24 |
24 |
|
| 25 |
|
-* **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>>doc:Software Engineering.Agile.Extreme Programming.Acceptance Tests.WebHome]]. |
| 26 |
|
-* **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. |
|
25 |
+* **High-level business requirements** defined by the customer in project requirements. Tests are essentially requirements translated into code. And customer requirements are typically translated into [[Acceptance Tests>>doc:Software Engineering.Agile.Extreme Programming.Acceptance Tests.WebHome]]. |
|
26 |
+* **Lower-level technical requirements** 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. |
| 27 |
27 |
* **Happy Path Requirements**: Always test scenarios where a user story works as expected. |
| 28 |
28 |
* **Unhappy Path Requirements**: Test scenarios where things do not go as planned. This includes |
| 29 |
29 |
** **Edge cases**: Test for maximum/minimum values, nulls, invalid input outside the allowed range, zeros, negative numbers, empty lists, and values with special meaning. |
| ... |
... |
@@ -31,8 +31,8 @@ |
| 31 |
31 |
** **Failure injection (chaos engineering)**: Perform chaos engineering to test the robustness of the system against unusual conditions. This includes actions such as killing processes, shutting down servers, disconnecting networks, simulating insufficient hardware resources (CPU, memory, disk space), and even simulating entire data center failures due to disasters. Ensure that the system remains functional, available, and able to recover automatically. |
| 32 |
32 |
** **Security requirements**: Simulate potential attack scenarios and verify that the software can withstand them, ensuring robust security measures. |
| 33 |
33 |
* **Performance requirements**: Interactions with software often need to be completed in a certain amount of time. |
| 34 |
|
-* **Load Requirements**: Verify that the software can handle the expected number of requests per second under normal operating conditions. |
| 35 |
|
-* **Stress Testing**: Run tests with an unusually high number of requests to determine the system's breaking point and ensure that it can handle extreme load conditions without catastrophic failure. |
|
34 |
+* **Load requirements**: Verify that the software can handle the expected number of requests per second under normal operating conditions. |
|
35 |
+* **Stress requirements**: Run tests with an unusually high number of requests to ensure that the system can handle extreme load conditions without catastrophic failure and to determine its breaking point. |
| 36 |
36 |
|
| 37 |
37 |
=== Table of Contents === |
| 38 |
38 |
|
