Mobile apps architecture at Tuenti

Mobile apps architecture & testing at Tuenti

Transcript

1. Joaquin Engelmo kini@tuenti.com Mobile apps at Tuenti “Architecture and Testing”
2. Tuenti Apps Android iOS
3. Tuenti Apps Android iOS
4. 76% 24%
6. rchitecture A
7. What was wrong? • 0 structure • Connected domain • API Requests from Activities and Fragments • Business Logic everywhere • Network operations updating data repositories • Data repositories in memory • Tons of duplicated code.
8. What are we going to use? • Clean Architecture • S.O.L.I.D • Dependency Injection
9. Did you said ‘Clean’?
10. Uncle Bob Clean https://www.youtube.com/watch?v=WpkDN78P884 http://blog.8thlight.com/uncle-bob/2012/08/13/the-clean-architecture.html
11. Tuenti Clean
12. Tuenti Clean
13. Tuenti Clean
14. Tuenti Clean
15. Tuenti Clean
16. Did you said ’SOLID’ too?
17. Uncle Bob S.O.L.I.D. http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod • Single Responsibility • Open-Close • Liskov Substitution • Interface Segregation • Dependency Inversion
19. Talk is cheap. Show me the code.
21. esting T
22. Testability Quick review
23. Testability Quick review
24. Testability Quick review
25. Testability Quick review
26. Testability Quick review • Mixing object graph construction with application logic • Ask for things, don’t look for things • Doing work in constructor • Global State/Singletons • Static methods
27. By Martin Fowler http://martinfowler.com/bliki/TestPyramid.html
28. • Black-box oriented tests • End to end • Instrument deployed app in phone/simulator • No tests doubles can be used • Needs a full and provisionable server environment • Slow tests Acceptance Tests Concepts
29. Acceptance Tests Environment
30. Acceptance Tests Lifecycle • Device data clean-up • App get launched • Test gets executed • Result and artifacts gets saved
31. • Outside of the emulator (JVM) • No need external env set up • Tests run in build time • App context • Use test doubles • Slower tests than unit tests Integration Tests Concepts
32. Integration Tests Environment
33. • Create App (onCreate) • Test setUp (@Before) • Test method • Test tearDown (@After) • Terminate App (onTerminate) Integration Tests Lifecycle
34. • JVM • Application classes in isolation • Test doubles • No app context • Build time • Really fast tests Unit Tests Concepts
35. Unit Tests Environment • Fast • Isolated • Repeatable • Self-Verifing • Timely
36. Unit Tests Lifecycle • Test setUp (@Before) • Test method • Test tearDown (@After)
37. Thanks!