Skip to Content

Changes for page Testing

Last modified by chrisby on 2024/06/20 14:42
From version 4.26
edited by chrisby
on 2024/04/01 13:18
Change comment: There is no comment for this version
To version 4.27
edited by chrisby
on 2024/05/18 09:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -29,7 +29,7 @@
29 29  ** **Performance requirements**
30 30  ** **Security requirements**
31 31  ** **Load requirements**, when software is expected to handle a certain number of requests per second.
32 -* 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.
32 +* 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.
33 33  
34 34  === Table of Contents ===
35 35