Skip to Content

Changes for page Testing

Last modified by chrisby on 2024/06/20 14:42
From version 4.10
edited by chrisby
on 2023/11/04 11:28
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
... ... @@ -31,3 +31,9 @@
31 31  ** **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.
32 32  ** **Performance requirements**
33 33  ** **Security requirements**
34 +** **Load requirements**, when software is expected to handle a certain number of requests per second.
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 +
37 +=== Related Topics ===
38 +
39 +See also the articles on [[Test-Driven Development>>doc:Software Engineering.Agile.Extreme Programming.Test-Driven Development.WebHome]] and [[Acceptance Testing>>doc:Software Engineering.Agile.Extreme Programming.Acceptance Tests.WebHome]].