Skip to Content

Changes for page Mocking

Last modified by chrisby on 2023/11/28 22:32
From version 1.10
edited by chrisby
on 2023/11/28 22:29
Change comment: There is no comment for this version
To version 1.8
edited by chrisby
on 2023/06/04 10:13
Change comment: Update document after refactoring.

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,9 @@
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. 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.
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.
4 4  
6 +=== ===
5 5  
6 6  === Benefits of Mocking ===
7 7  
... ... @@ -27,7 +27,7 @@
27 27  
28 28  === Tips ===
29 29  
30 -* **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.
31 31  * Aim for a **minimal number of dependencies in a unit** for easier testing and mocking:
32 32  ** 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.
33 33  ** Prefer many small classes/units to one large one for easier testing.