Skip to Content

Changes for page Mocking

Last modified by chrisby on 2023/11/28 22:32
From version 1.4
edited by chrisby
on 2023/05/29 12:21
Change comment: There is no comment for this version
To version 1.9
edited by chrisby
on 2023/06/18 10:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -Software Architecture.Testing.WebHome
1 +Software Engineering.Testing.WebHome
Content
... ... @@ -3,6 +3,8 @@
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 +
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,6 +11,8 @@
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  
16 +=== ===
17 +
14 14  === Types of Mocks ===
15 15  
16 16  (% style="text-align: justify;" %)
... ... @@ -18,12 +18,14 @@
18 18  
19 19  * **Stubs**: Simplest form, returning a hardcoded value or providing an empty method body.
20 20  * **Fake object**: Include minimal logic to handle different case scenarios.
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.
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.
23 23  
28 +=== ===
29 +
24 24  === Tips ===
25 25  
26 -* **Mock third-party libraries for unit tests** to ensure proper unit functionality. Instead, use these libraries in component and integration tests.
32 +* **Mock third-party libraries in unit tests** to ensure proper unit functionality. However, they should not be mocked in component and integration tests.
27 27  * Aim for a **minimal number of dependencies in a unit** for easier testing and mocking:
28 28  ** 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.
29 29  ** Prefer many small classes/units to one large one for easier testing.