| ... |
... |
@@ -30,7 +30,8 @@ |
| 30 |
30 |
** **Failure Injection**: For example, at the operational level, this could include actions such as killing processes, shutting down servers, disconnecting networks, insufficient hardware resources (CPU, memory, disk space), even simulating entire data centers failing due to disasters, etc., while verifying that the system is still fully functional, available, and able to automatically recover. |
| 31 |
31 |
** **Security requirements**: For example, simulate all potential attack scenarios and verify that the software can withstand them. |
| 32 |
32 |
* **Performance requirements**: Interactions with software often need to be completed in a certain amount of time. |
| 33 |
|
-* **Load requirements**, when software is expected to handle a certain number of requests per second. |
|
33 |
+* **Load Requirements**: Verify that the software can handle the expected number of requests per second under normal operating conditions. |
|
34 |
+* **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 |
34 |
|
| 35 |
35 |
=== Table of Contents === |
| 36 |
36 |
|
