Skip to Content

Changes for page Testing

Last modified by chrisby on 2024/06/20 14:42
From version 4.48
edited by chrisby
on 2024/05/26 12:09
Change comment: There is no comment for this version
To version 4.51
edited by chrisby
on 2024/05/26 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
1 1  === Foreword ===
2 2  
3 3  (% style="text-align: justify;" %)
4 -The chapters presented here are a concise summary of more high-level knowledge. It is recommended that you are familiar with writing very basic tests and mocks before reading on.
4 +The chapters presented here are a concise summary of more high-level knowledge about testing. It is recommended that you are familiar with writing very basic tests and mocks before reading on.
5 5  
6 6  === Benefits of Testing ===
7 7  
... ... @@ -26,7 +26,7 @@
26 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.
27 27  * You should always test **happy path** requirements, where a user story works as expected, and **unhappy path** requirements. For the latter, we need **chaos engineering**, i.e., verifying that a system can withstand unusual conditions makes it robust against failure and misuse.
28 28  ** **Border cases** that could theoretically occur, such as maximum/minimum values, nulls, invalid input outside the permissible value range, zeroes, negative numbers, empty lists and values with special meaning.
29 -** **Error cases**: Exceptions, dependencies returning errors, a file access or existence problem, network problems etc. Anything could could potentially go wrong.
29 +** **Error cases**: Exceptions, dependencies returning errors, a file access or existence problem, network problems etc. Anything that could potentially go wrong.
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.