Skip to Content

Changes for page Testing

Last modified by chrisby on 2025/07/04 11:27
From version 4.18
edited by chrisby
on 2024/04/01 12:41
Change comment: There is no comment for this version
To version 4.17
edited by chrisby
on 2024/04/01 12:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -31,7 +31,7 @@
31 31  ** **Performance requirements**
32 32  ** **Security requirements**
33 33  ** **Load requirements**, when software is expected to handle a certain number of requests per second.
34 -* At any level of abstraction, you should always test **happy path** requirements, where everything works as expected, and **unhappy path** requirements, where something goes wrong or an unusual input is provided. Writing tests for the latter makes the software robust against failures and misuse.
34 +* At any level of abstraction, you should always test **happy path** requirements, where everything works as expected, and **unhappy path** requirements, where something goes wrong or an unusual input is provided. Writing tests for the latter makes the software robust against misuse.
35 35  
36 36  === Related Topics ===
37 37