| ... |
... |
@@ -1,9 +1,7 @@ |
| 1 |
1 |
=== Purpose === |
| 2 |
2 |
|
| 3 |
|
-* Mocking simplifies unit testing by replacing the dependencies of the unit being tested with simplified, simulated versions called mocks. |
| 4 |
|
-* Example: Consider a unit under test that relies on a database. In testing, the database can be mocked to return a static value, eliminating the need for an actual database. |
|
3 |
+* **Mocking simplifies unit testing by replacing the dependencies** of the unit being tested with simplified, simulated versions called mocks. Example: Consider a unit under test that relies on a database. In testing, the database can be mocked to return a static value, eliminating the need for an actual database. |
| 5 |
5 |
|
| 6 |
|
-=== === |
| 7 |
7 |
|
| 8 |
8 |
=== Benefits of Mocking === |
| 9 |
9 |
|
| ... |
... |
@@ -29,7 +29,7 @@ |
| 29 |
29 |
|
| 30 |
30 |
=== Tips === |
| 31 |
31 |
|
| 32 |
|
-* **Mock third-party libraries in unit tests** to ensure proper unit functionality. Instead, use these libraries in component and integration tests. |
|
30 |
+* **Mock third-party libraries in unit tests** to ensure proper unit functionality. However, they should not be mocked in component and integration tests. |
| 33 |
33 |
* Aim for a **minimal number of dependencies in a unit** for easier testing and mocking: |
| 34 |
34 |
** Limit dependencies in a unit in a similar way to the best practices for function arguments: the fewer the better, with an absolute maximum of three. |
| 35 |
35 |
** Prefer many small classes/units to one large one for easier testing. |
