Skip to Content

Changes for page Testing

Last modified by chrisby on 2024/06/20 14:42
From version 4.5
edited by chrisby
on 2023/10/11 11:08
Change comment: There is no comment for this version
To version 4.4
edited by chrisby
on 2023/10/11 11:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -33,7 +33,7 @@
33 33  Every functionality you expect the software to provide at any moment. You should test:
34 34  
35 35  * **Functional Requirements**
36 -** **High-level use cases** that are defined in project requirements by the customer. Tests are actually requirements translated into code. And customer requirements are usually translated into acceptance tests.
36 +** **High-level use cases** that are defined in project requirements. Tests are actually specification translated into code.
37 37  * **Non-Functional Requirements**
38 38  ** **Lower-level use cases** derived from high-level project use cases that are not directly visible to end users, but form the backbone of software functionality. This includes the expected behavior of the underlying functions, classes, modules, and components.
39 39  ** **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.