Skip to Content

Changes for page Testing Principles

Last modified by chrisby on 2024/04/01 12:52
From version 1.1
edited by chrisby
on 2023/05/29 09:02
Change comment: There is no comment for this version
To version 1.2
edited by chrisby
on 2023/05/29 09:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,13 +11,3 @@
1 -What should be tested? ➡ Every functionality you expect the software to provide at any moment. You should test:
2 -
3 -* **User Cases**
4 -** Defined in project requirements
5 -** 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.
6 -* **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.
7 -
8 -
9 -=== Principles ===
10 -
11 11  * **High Coverage**:
12 12  ** **Code Coverage** Definition: The percentage of classes/methods/lines of code executed during testing. There is class coverage, method coverage and line coverage, the latter being the most important.
13 13  ** **100% code coverage** is the goal. Untested code is insecure code and prone to bugs.