Skip to Content

Changes for page Testable Design

Last modified by chrisby on 2024/09/19 10:50
From version 3.7
edited by chrisby
on 2023/11/04 11:07
Change comment: There is no comment for this version
To version 3.9
edited by chrisby
on 2023/11/05 19:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,5 @@
1 -## What Makes Code Testable?
1 +### What Makes Code Testable?
2 2  
3 -### Core aspects
4 -
5 5  * **Object-Oriented**: Although both procedural and functional programming paradigms support testing, managing test complexity can become a challenge as the system scales. As complexity increases, maintaining test isolation becomes more difficult. An effective strategy is to use object-oriented techniques that encapsulate complex logic within hierarchies of classes, creating testable units that hide their internal complexity behind interfaces. Wrapping procedural or functional code in classes can combine the strengths of several paradigms. Any code base that reaches a certain level of complexity can benefit from an object-oriented approach to improve testability.
6 6  * **Minimal number of dependencies** in a unit for low complexity.
7 7  * **Dependencies are injectable** via [[constructor injection or setter injection|doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]].
... ... @@ -8,11 +8,6 @@
8 8   * Injectable is equivalent to mockable. Mocks make testing with dependencies much easier. IoC containers are good tools for building many applications consisting of classes into which dependencies need to be injected.
9 9   * Injectable promotes decoupling. Dependency injection allows for more flexible and extensible code through interchangeable dependencies.
10 10  * **Outsource code that is difficult to test.** For example, network connections to external services should not be part of unit or component tests and should therefore be mocked away.
11 -
12 -###
13 -
14 -### Additional Details
15 -
16 16  * **Avoid direct instantiation of objects** in units being tested; doing so tightly couples the implementation and restricts substitutability. Use **factories** and **dependency injections** instead.
17 17  * **Favor dependency injection over service lookups.**
18 18  * **Avoid reflections** undermining encapsulation.
... ... @@ -27,12 +27,3 @@
27 27   * Develop self-contained modules: Each module should be a self-contained unit of functionality. New features should be introduced by creating new modules.
28 28  * **Avoid the singleton design pattern** because its private constructor prevents mocking. Consider a `getInstance()` method that returns an interface type instead.
29 29  * **Favor composition over inheritance.** Use inheritance only for polymorphism, as it is less flexible than composition. Composition should be the primary approach to code reuse.
30 -
31 -###
32 -
33 -### Testable Architecture
34 -
35 -An important part of a testable architecture is the **Humble Object Pattern**. The pattern emphasizes the isolation of complex to test aspects (such as GUI interactions), keeping them 'humble' with minimal logic:
36 -
37 -* **Minimize logic of hard-to-test layers** such as GUIs to keep them as thin as possible, focusing primarily on user interaction, routing, and data transformation.
38 -* **Maximize business logic**: You can move logic to the business logic/service layer, which is easier to test, improving overall testability.