| ... |
... |
@@ -3,8 +3,6 @@ |
| 3 |
3 |
* Mocking simplifies unit testing by replacing the dependencies of the unit being tested with simplified, simulated versions called mocks. |
| 4 |
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. |
| 5 |
5 |
|
| 6 |
|
-=== === |
| 7 |
|
- |
| 8 |
8 |
=== Benefits of Mocking === |
| 9 |
9 |
|
| 10 |
10 |
* Isolation of units to test each unit separately, dramatically reducing complexity and increasing test execution speed by replacing loaded modules with mocks. |
| ... |
... |
@@ -13,8 +13,6 @@ |
| 13 |
13 |
* Injection of test-specific behaviors not present in production code. |
| 14 |
14 |
* Enables the simulation of indirect dependencies by letting mocks return other mocks. |
| 15 |
15 |
|
| 16 |
|
-=== === |
| 17 |
|
- |
| 18 |
18 |
=== Types of Mocks === |
| 19 |
19 |
|
| 20 |
20 |
(% style="text-align: justify;" %) |
| ... |
... |
@@ -22,11 +22,9 @@ |
| 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. |
|
21 |
+* **Spy**: Injected to capture interaction data with fake objects when such data is not directly accessible. |
|
22 |
+* **Mock objects**: Contain complex logic, simulate behaviors such as computation and exception handling, and even run tests. |
| 27 |
27 |
|
| 28 |
|
-=== === |
| 29 |
|
- |
| 30 |
30 |
=== Tips === |
| 31 |
31 |
|
| 32 |
32 |
* **Mock third-party libraries in unit tests** to ensure proper unit functionality. Instead, use these libraries in component and integration tests. |
