Skip to Content

Changes for page Mocking

Last modified by chrisby on 2023/11/28 22:32
From version 1.6
edited by chrisby
on 2023/05/29 15:38
Change comment: There is no comment for this version
To version 1.10
edited by chrisby
on 2023/11/28 22:29
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
... ... @@ -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  
... ... @@ -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**: 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.
23 +* **Spy**: Records internal data of the unit being tested when such data is not directly accessible.
24 +* **Mock object**: Contains complex logic, simulates behaviors such as computation and exception handling, and can 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. 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.