| ... |
... |
@@ -3,6 +3,7 @@ |
| 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 |
+ |
| 6 |
6 |
=== Benefits of Mocking === |
| 7 |
7 |
|
| 8 |
8 |
* Isolation of units to test each unit separately, dramatically reducing complexity and increasing test execution speed by replacing loaded modules with mocks. |
| ... |
... |
@@ -11,9 +11,9 @@ |
| 11 |
11 |
* Injection of test-specific behaviors not present in production code. |
| 12 |
12 |
* Enables the simulation of indirect dependencies by letting mocks return other mocks. |
| 13 |
13 |
|
|
15 |
+ |
| 14 |
14 |
=== Types of Mocks === |
| 15 |
15 |
|
| 16 |
|
-(% style="text-align: justify;" %) |
| 17 |
17 |
Stubs are by far the most common type of mock. Keep your tests as simple as possible. Make them more complex only when necessary. |
| 18 |
18 |
|
| 19 |
19 |
* Stubs: Simplest form, returning a hardcoded value or providing an empty method body. |
| ... |
... |
@@ -21,6 +21,7 @@ |
| 21 |
21 |
* Spy: Injected to capture interaction data with fake objects when such data is not directly accessible. |
| 22 |
22 |
* Mock objects: Contain complex logic, simulate behaviors such as computation and exception handling, and even run tests. |
| 23 |
23 |
|
|
25 |
+ |
| 24 |
24 |
=== Tips === |
| 25 |
25 |
|
| 26 |
26 |
* Mock third-party libraries for unit tests to ensure proper unit functionality. Instead, use the third-party libraries in component and integration tests. |
