... |
... |
@@ -22,14 +22,14 @@ |
22 |
22 |
|
23 |
23 |
* **Stubs**: Simplest form, returning a hardcoded value or providing an empty method body. |
24 |
24 |
* **Fake object**: Include minimal logic to handle different case scenarios. |
25 |
|
-* **Spy**: Records internal data of the unit being tested when such data is not directly accessible. |
26 |
|
-* **Mock object**: Contains complex logic, simulates behaviors such as computation and exception handling, and can even run tests. |
|
25 |
+* **Spy**: Injected to capture interaction data with fake objects when such data is not directly accessible. |
|
26 |
+* **Mock objects**: Contain complex logic, simulate behaviors such as computation and exception handling, and even run tests. |
27 |
27 |
|
28 |
28 |
=== === |
29 |
29 |
|
30 |
30 |
=== Tips === |
31 |
31 |
|
32 |
|
-* **Mock third-party libraries in unit tests** to ensure proper unit functionality. However, they should not be mocked in component and integration tests. |
|
32 |
+* **Mock third-party libraries in unit tests** to ensure proper unit functionality. Instead, use these libraries 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. |