How Android Testing changed how we think about death...

"Irreproducible bugs become highly reproducible right after delivery to the customer". This is something that happens "almost" everyday.

It is well known that testing offers significant advantages as a development practice and helps ensure higher quality code with fewer defects.

Unfortunately, testing Android apps can be challenging, so in this session we are gonna talk about available tools and practices that could help us accomplish our goals.

Transcript

1. How ANDROID TESTING changed how we think about death… @fernando_cejas Code samples: https://github.com/android10/Inside_Android_Testing https://github.com/android10/AndroidApplicationTestingSample
2. Who am I… •  Software Engineer •  GDG Barcelona Organizer •  Android lover •  Geek •  Gintonic fan… …y un pelotudo…
3. Agenda?
4. Why testing..WTF? •  Testing increases the level of confidence in your code. •  Testing makes it possible to write new code, and refactor existing code, without worrying that you’ve broken existing functionality.
5. Martin Fowler: "...test-doubles ... preprogrammed with expectation" What is this mock thing?
6. Mockito is a mocking framework that tastes really good. Mockito doesn't give you hangover because the tests are very readable and they produce clean verification errors. GIVE A WARM WELCOME TO… mockito
7. Mockito Build-operate-check pattern
8. Mock initizalition
9. Initizalition using mockito test runner
10. Let’s verify some behaviour
11. Argument matchers
12. Verifying number of invocations / at least x / never
13. Making sure interaction(s) never happened on mock
14. Spying on real objects
15. Sounds familiar???
16. Allows you to run your android code on JVM. Allows loading of Android Classes in pure Java Projects. TO THE RESCUE…
17. Shadow Objects!
18. View and Resource Loading…
19. Shadow Activity Shadow ImageView
20. •  Uses real Android SDK code •  Styles and themes supported •  System resources are available •  Performance improved •  Bugs fixed Robolectric 2.0+
21. Perform click Sample
22. Started Activity test Should have fragment test
23. Device Configuration Sample
24. Network sample Robolectric acts as a proxy!!!
25. Creating your own shadows
26. Creating your own shadows
27. Creating your own shadows
28. •  A library by square (FTW!) •  It gives a chainable (or “fluent”) syntax for checking assertions. •  Makes tests easier to write (and read!). FEST Android
29. Sample: code to modify a bitmap
30. Assertions with FEST
31. Dependency injection is a software design pattern that allows the removal of hard-coded dependencies and makes it possible to change them, whether at run-time or compile-time Dependency what?
32. Dagger Directed Acyclic Graph
33. Dagger Graph sample
34. Dagger sample
35. Declare dependencies
36. Satisfy dependencies
37. Build the graph
38. Modules
39. Spoon •  Acceptance tests (black box) •  Automation of test execution across multiple devices •  Aggregation of the results
40. Spoon •  Aggregation of screenshots while your tests are running
41. •  Robojuice •  Robotium •  Android Testing Framework •  UI Automator •  Monkey Runner More tools…
42. WRITE TESTS!!! •  Simplify your architecture •  Have a robust testing strategy •  Use continuous integration tools •  Mock/stub functionality •  Create your own test runner Best practices and some advice…
44. Questions?
45. @fernando_cejas https://github.com/android10 jobs@tuenti.com http://corporate.tuenti.com/es/dev/blog THANKS!!!