Clean Android Code for Unit Testing

GDG Kaohsiung 2016/07/03

Transcript

1. Clean Android Code for Unit Testing York Wu 2016.07.03
2. Sample Project https://github.com/yorkwu0318/GDGK_Testing_Sample Unit testing PPT https://goo.gl/sTaFlm CI 環境建置 http://goo.gl/nAAfhF CI PPT https://goo.gl/dSsMyU
3. Why Testing?
4. Testing Type Type Subtype Tool Unit Tests Local Unit Test Junit Instrumented unit tests JVM
5. Testing Type Type Subtype Tool Integration Tests Components within your app only Espresso Cross-app Components UI Automator
6. Testing Type Other Integration Test Unit Test
7. Demo 1
8. How to test it?
9. Model
10. Demo 2
15. UI Test!!
18. multi-thread
19. Fix it: register Idling Resource
21. How Testing
22. Hard to test code 1. Android Framework 2. Async Task
23. Write Testable Code 1. Dependency Injection 2. Base on MVP Pattern (Clean Architecture)
24. Dependency Injection Demo3
26. build.gradle Ref Android Testing Codelab Android Architecture Blueprints
29. but unit testing..
30. we need better architecture • MVC • MVP • MVVM (Databinding)
31. MVC C M V logic Activty LoginModel Activty, View
32. MVC C Activty M LoginModel V Activty, View logic Activity and logic can’t be divided
33. MVP P LoginPresenter M LoginModel V Activty, View logic
34. MVP P LoginPresenter M LoginModel V Activty, View logic
37. Demo4 - MVP
39. MVVM VM LoginViewModel M LoginModel V Activty, View logic
40. Demo4 - MVVM
42. PreseterTest
43. Optimization • Data Binding • Retrofit 2 • RxJava
44. Retrofit 2 + RxJava Mock
45. RxJava mock prod
46. RxJava
47. DataBinding 1. remove findViewById( ) 2. remove view.setValue( ) 3. simply ui logic 4. demo /ex
48. Testing Strategy • Mock data • Mock library
50. TDD 1. new request 2. add tests 3. red to green practice: add new request on /ex ex: email/password regular email/password length
51. Summary 1. testing is used to protect code logic. 2. testing is not used to test server API result!! 3. testing needs the testable code. 4. testable code needs good-designed code.
52. Q&A