Skip to Content

Changes for page Mocking

Last modified by chrisby on 2023/11/28 22:32
From version 1.7
edited by chrisby
on 2023/05/29 15:41
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
... ... @@ -29,7 +29,7 @@
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.
32 +* **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.