Changes for page Testing

Last modified by chrisby on 2024/06/20 14:42

From version 4.34

edited by chrisby
on 2024/05/26 11:56

Change comment: There is no comment for this version

To version 4.35

edited by chrisby
on 2024/05/26 11:57

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -27,7 +27,7 @@
  * **Chaos Engineering**: Verifying that a system can withstand unusual conditions makes it robust.
  ** **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.
  ** You should always test **happy path** requirements, where a user story works as expected, and **unhappy path** requirements, where something goes wrong, such as a dependency returning an error, a file access problem, unusual input, network problems and so on.  Writing tests for the latter makes the software robust against failure and misuse.
--** On an operational level, this could include measure such as killing processes, shutting down server, cutting of networks, etc.
++** 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.
  * If needed:
  ** **Performance requirements**
  ** **Security requirements**