| ... |
... |
@@ -28,8 +28,8 @@ |
| 28 |
28 |
* **Chaos Engineering**: Verifying that a system can withstand unusual conditions makes it robust against failures and misuse. |
| 29 |
29 |
** **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, dependency returning errors, a file access problem, network problems etc. Anything could could potentially go wrong. |
| 30 |
30 |
** For example, at the operational level, this could include actions such as killing processes, shutting down servers, disconnecting networks, even simulating entire data center failures due to disasters, etc., while verifying that the system is still fully functional, available, and able to automatically recover. |
| 31 |
|
-** **Performance requirements**: Simulate heavy loads and make sure the system can handle them.Simulate high loads and ensure the system can handle it. |
| 32 |
|
-** **Security requirements**: For example, simulate attack scenarios. |
|
31 |
+** **Security requirements**: For example, simulate all potential attack scenarios and verify that the software can withstand them. |
|
32 |
+* **Performance requirements**: |
| 33 |
33 |
* **Load requirements**, when software is expected to handle a certain number of requests per second. |
| 34 |
34 |
|
| 35 |
35 |
=== Table of Contents === |
