| ... |
... |
@@ -3,16 +3,9 @@ |
| 3 |
3 |
(% style="text-align: justify;" %) |
| 4 |
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 Engineering.Architecture.Dependency Injection.WebHome]] before reading on. |
| 5 |
5 |
|
| 6 |
|
-=== === |
|
6 |
+(% style="text-align: justify;" %) |
|
7 |
+The **ultimate goal of testing** is to reduce costs and increase productivity. Development with testing is faster and safer than without. |
| 7 |
7 |
|
| 8 |
|
-=== General === |
| 9 |
|
- |
| 10 |
|
-* **Ultimate Goal** of testing: Reduce costs and increase productivity. Development with testing is faster and safer than without. |
| 11 |
|
-* **Definition 'Production Code':** Code that provides the functionalities of a system. |
| 12 |
|
-* **Definition 'Test Code':** Often referred to as "tests", it is written to verify the correct functionality of the production code. |
| 13 |
|
- |
| 14 |
|
-=== === |
| 15 |
|
- |
| 16 |
16 |
=== Benefits of Testing === |
| 17 |
17 |
|
| 18 |
18 |
* **Quality Assurance** |
| ... |
... |
@@ -25,8 +25,6 @@ |
| 25 |
25 |
** Tests serve as the most up-to-date form of code documentation, capturing the expected behavior of the production code in its current state or of a third-party library. |
| 26 |
26 |
** Good tests are quick and easy to understand because they are written in an expressive language that developers speak fluently. In addition, the actual documentation is often simply skipped over. |
| 27 |
27 |
|
| 28 |
|
-=== === |
| 29 |
|
- |
| 30 |
30 |
=== What should be tested? === |
| 31 |
31 |
|
| 32 |
32 |
(% style="text-align: justify;" %) |
