| ... |
... |
@@ -1,13 +1,4 @@ |
| 1 |
|
-=== Foreword === |
| 2 |
|
- |
| 3 |
|
-(% style="text-align: justify;" %) |
| 4 |
|
-The chapters presented here are a concise summary of more theoretical and high-level knowledge. It is recommended that you are familiar with writing very basic tests and mocks, and understand the concepts of polymorphism and [[dependency injection>>doc:Software Architecture.Dependency Injection.WebHome]]. |
| 5 |
|
- |
| 6 |
|
-=== === |
| 7 |
|
- |
| 8 |
|
-=== General === |
| 9 |
|
- |
| 10 |
|
-* **Ultimate Goal** of testing: Reduce costs and increase productivity. |
|
1 |
+* **Ultimate Goal**: Reduce costs and increase productivity. |
| 11 |
11 |
* **Definition 'Production Code':** Code that provides functionality to meet project requirements. |
| 12 |
12 |
* **Definition 'Test Code':** Often referred to as "tests", it is written to verify the correct functionality of the production code. |
| 13 |
13 |
|
| ... |
... |
@@ -28,10 +28,9 @@ |
| 28 |
28 |
|
| 29 |
29 |
=== What should be tested? === |
| 30 |
30 |
|
| 31 |
|
-(% style="text-align: justify;" %) |
| 32 |
32 |
Every functionality you expect the software to provide at any moment. You should test: |
| 33 |
33 |
|
| 34 |
34 |
* **Use Cases** |
| 35 |
|
-** Use cases defined in project requirements |
| 36 |
|
-** Lower-level use cases derived from the high-level project use cases. For example, expected behavior of functions, classes, modules, and components that users of the software do not see. |
|
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. |
| 37 |
37 |
* **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. |
