Skip to Content

Changes for page Testing

Last modified by chrisby on 2025/07/04 11:27
From version 4.13
edited by chrisby
on 2023/12/29 21:45
Change comment: There is no comment for this version
To version 4.12
edited by chrisby
on 2023/12/29 21:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -32,7 +32,7 @@
32 32  ** **Performance requirements**
33 33  ** **Security requirements**
34 34  ** **Load requirements**, when software is expected to handle a certain number of requests per second.
35 -* 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 +* In general, 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.
36 36  
37 37  === Related Topics ===
38 38