Skip to Content

Changes for page Testing

Last modified by chrisby on 2024/06/20 14:42
From version 2.3
edited by chrisby
on 2023/05/29 09:04
Change comment: There is no comment for this version
To version 2.4
edited by chrisby
on 2023/05/29 09:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -21,7 +21,7 @@
21 21  
22 22  Every functionality you expect the software to provide at any moment. You should test:
23 23  
24 -* **User Cases**
24 +* **Use Cases**
25 25  ** Defined in project requirements
26 26  ** Use cases derived from the high-level project use cases. For example, expected behavior of functions, classes, modules and components that the user does not see.
27 27  * **Border cases** that could theoretically always occur, such as maximum/minimum values, nulls, invalid input, nulls, negative numbers, empty lists, values with special meaning, exceptions, etc.