Skip to Content

Changes for page Testing

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

Summary

Details

Page properties
Content
... ... @@ -2,6 +2,8 @@
2 2  * **Definition 'Production Code':** Code that provides functionality to meet project requirements.
3 3  * **Definition 'Test Code':** Often referred to as "tests", it is written to verify the correct functionality of the production code.
4 4  
5 +=== ===
6 +
5 5  === Benefits of Testing ===
6 6  
7 7  * **Quality Assurance**
... ... @@ -11,6 +11,15 @@
11 11  * **Testable Design**
12 12  ** Writing tests automatically enforces design best practices, resulting in a 'testable design' and higher quality code. Good code and architecture are testable, and vice versa.
13 13  * **Documentation**
14 -** (((
15 -Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state.
16 -)))
16 +** Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state.
17 +
18 +=== ===
19 +
20 +=== What should be tested? ===
21 +
22 +Every functionality you expect the software to provide at any moment. You should test:
23 +
24 +* **User Cases**
25 +** Defined in project requirements
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 +* **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.