simple way for testing and modular programming

1. DESIGN PATTERN
BY LUIS GINANJAR

2. COMPLICATED MANUAL TEST PER CASE
TOO MANY HUMAN ERROR
Module A
Case 1
Case 2
Case 3

3. SOLUTION : UNIT TEST
WE CREATE TEST BY CODE, SO IT CAN’T FORGET OR LOST
Module A
Case 1
Case 2
Case 3
UNIT TEST

4. UNIT TEST BENEFIT
Quick Feedback
Simplifies Integration
Form of sample code
Modular object
Saves development time
Inspires confidence
Better Design

5. PROBLEM UNIT TEST :
DEPENDENCY TO ANOTHER OBJECT
Module A
Case 1
Case 2
Case 3
UNIT TEST
DB
API
Module
B

6. SOLUTION : INTERFACE
Module A
IDB
IAPI
IModule
B
DB
API
Module
B
Interface

7. INTERFACE WITH MOCK
CHANGE DEPENDENCY TO FAKE OBJECT, SO WE CAN FOCUS TESTING ON
PRIMARY OBJECT
Module A
IDB
IAPI
IModule
B
Fake
DB
Fake
API
Fake
Module
B
Interface
Unit Test

8. Interfac
e
IMPLEMENTATION
Module A
Fake ModuleUnit Test
OF Initiate ModuleAGetModuleA()
Real Module
App
(OF as assembler module / object, OF can determine create real or fake module / object)

9. THIS TECHNIQUE IS CALLED :
DEPENDENCY INJECTION
Don't initiate specific object or specific implementation inside,
to prevent tight coupling. ~Uncle Bob

10. UNIT TEST AS DOCUMENTATION TECHNICAL SPEC
WE CAN REUSE SAME TEST AND INTERFACE FOR ANOTHER PLATFORM OR
LANGUAGE, SO WE CAN PREVENT REPEATING ERROR
Interface &
Unit Test
iOS Android