Android Application Development: Better, Faster, Stronger! at Devoxx 2013

Android Application Development hands-on lab @ Devoxx 2013

Transcript

1. Android Application Development: Better, Faster, Stronger!
2. Your hosts Filip Maelbrancke (@fmaelbrancke) Peter Kuterna (@peterkuterna) ! ! Consultants at iDA MediaFoundry (@iDAMediaFoundry) / XTi
3. Why this session?
4. First off... Why? What? How?
8. Avoid problems
9. You = McGuyver
10. Deployment pipeline Commit stage Automated test/QA stage Manual QA testing UAT test Production Capacity / load testing
11. Build pipeline Checkout / compile Unit tests Test coverage Code analysis Create deployable artifact Deploy for automatic QA test Trigger automated QA stage
12. IDE Eclipse ! IntelliJ ! Android Studio
13. Build Ant ! Maven ! Gradle
14. CI Jenkins ! Atlassian Bamboo ! Travis ! Teamcity
15. Testing JUnit / TestNG ! Mocking ! UI testing
16. Build system
17. Android project setup & build
    ant gradle
18. Android SDK build system
19. Gradle? why - goals Powerful build system declarative, flexible tooling API ! Unified across IDEs & CI servers ! Free / open source
20. Basics buildscript { ! repositories { ! mavenCentral() ! } ! dependencies { ! classpath ‘com.android.tools.build:gradle:0.6’ ! }! }! ! apply plugin: ‘android’! ! android { ! compileSdkVersion 19 ! buildToolsVersion ‘19.0.0’! }! !
21. Gradle tasks assemble debug / release ! check (test) check / connectedCheck ! build
22. Build types build / packaging customization debuggable flag ProGuard signing configuration source / resources overlay debug and release prebuilt
23. local dependencies dependencies { compile fileTree(dir: ‘libs’, include: ‘*.jar’) } android { ... }
24. remote dependencies repositories { mavenCentral() } android { ... } dependencies { instrumentTestCompile ‘com.squareup:fest-android:1.0.4’ compile file(‘libs/protobuf.jar’) }
25. multi-project setup MyProject/ | settings.gradle + app/ | build.gradle + libraries/ + lib1/ | build.gradle + lib2/ | build.gradle
26. android library Binary Bundle (.aar) - Uploadable to repositories Support for - assets - ProGuard rules - Custom Lint Rules - ...
27. build variants build variants product flavors
28. Device vs emulator Genymotion
29. Testing
30. Testing Manual testing is tedious ! Humans are not very good at testing ! But computers are...
31. “Computers are designed to do simple repetitive tasks. The second you have humans doing repetitive tasks, all the computers get together late at night and laugh at you...” Neil Ford
32. Manual vs Automated
33. Manual vs Automated
34. Early detection
35. Excuses We never make mistakes! The functionality is trivial Tests slow us down Management won’t let us
36. Unit test Isolated Repeatable Fast Self-documenting
37. Repeatability Tests need to be run by every developer (no matter what development stack he uses) Tests must not rely on the environment in which they are being run
38. Speed The shorter, the less distraction, less of an interruption to our workflow
39. Self documenting Testable code is clear and easy to follow No need to explain how a certain component works, we can just look at the test No need to write documentation
40. Self documenting Testable code is clear and easy to follow No need to explain how a certain component works, we can just look at the test No need to write documentation Tests = usage examples
41. Testing Automated testing
42. (Unit) testing in Android Android SDK (JUnit 3-based) Instrumentation tests ! Monkeyrunner The monkey UIAutomator + UIAutomatorViewer
43. Android instrumentation tests JUnit 3 ! import junit.framework.*; public class MyTestClass extends TestCase { public void testMethodName() throws Exception { } }
44. Android instrumentation tests Instrumentation = set of control methods or “hooks” in the Android system ! These hooks control an Android component independently of the normal lifecycle
45. Android instrumentation tests Application Activity Service Content Provider
46. Android instrumentation tests Isolate tests from the system: MockApplication MockContext MockResources MockContentProvider MockContentResolver MockPackageManager
47. Exercise
48. The monkey Generates pseudo-random stream of user events: clicks touches gestures system-level events ! stress test your app
49. The monkey command-line tool Basic configuration options, such as setting the number of events to attempt. Operational constraints, such as restricting the test to a single package. Event types and frequencies. Debugging options. ! $ adb shell monkey -p your.package.name -v 500 http://developer.android.com/tools/help/monkey.html
50. Exercise
51. UI testing UIAutomator ! ! ! ! Espresso
52. Third Party Tools
53. Robolectric Android core libraries depend upon the actual Android operating system
54. Robolectric AndroidTestCase needs an instance of the emulator to run ! Big time sink: - spin up emulator - deploy the APK - run the actual tests
55. Robolectric Replaces the behavior of code that would otherwise need an emulator / device Write JUnit tests without the baggage of a device ! Does this by using Shadow Classes (mock implementations of Android core libraries)
56. Exercise
57. Robolectric InstrumentationTestCase too slow / hard for unit testing? ! vs real device / speedy emulator
58. Robolectric advantages Unit testing fast and easy Make your own shadow objects JUnit 4 supported (Android = JUnit 3)
59. Robolectric disadvantages Does not cover all functionality (sensors, OpenGL, ...)
 → device needed Integration testing (interaction Activities - Services, camera app, ...)
60. Build system
61. Android project setup & build
    ant gradle
62. Android build system
63. Android Maven plugin https://code.google.com/p/maven-android-plugin/ <plugin> <groupId>com.jayway.maven.plugins.android.generation2</groupId> <artifactId>android-maven-plugin</artifactId> <version>3.8.0</version> </plugin>!
64. Maven “Software project management and comprehension tool” ! Builds your software and much more ! De-facto standard for Java software builds ! Convention over configuration ! Declarative rather than procedural
65. Maven and Android Android Maven Plugin – core tool ! M2Eclipse, m2e-android – for Eclipse users ! Maven Android SDK Deployer – for SDK libraries ! Maven Android Archetype – project templates
66. Gradle vs Maven Gradle Maven Build variants / product flavors ✔ ✖ Android test framework ✔ ✔ Robotium ✔ ✔ Robolectric ✔ ✔ UIAutomator / Monkey ✖ ✔ Code coverage ✖ ✔ Code quality (pmd, checkstyle, findbugs, lint) ✔ ✔ Aggregation ✔ ✔ Source: https://github.com/stephanenicolas/Quality-Tools-for-Android
67. Mocks Easymock ! Mockito - uses DexMaker to generate mock classes
68. Mocking Mocking Frameworks allow us to test the code you want, without its dependencies. Mock objects can simulate the behaviour of complex objects. Mock objects isolate the unit of code you are testing.
69. Mockito Prepare the mock + behavior ! Test the method of interest ! Validate that the mock saw what we expected / didn’t see anything unexpected
70. Exercise
71. Robotium Extension of the Android testing framework Makes it easier to write UI tests Inherits from ActivityInstrumentationTestCase2 Main class for testing is Solo Solo is initialized with the instrumentation of the testcase and the activity to test https://code.google.com/p/robotium/
72. Exercise
73. Android FEST Syntactic sugar Extension of the FEST library Fluent syntax for checking assertions Makes tests easier to read/write ! https://github.com/square/fest-android
74. Android FEST assertEquals(View.GONE, view.getVisibility()); assertThat(view).isGone(); expected: <8> but was: <4> Expected visibility <gone> but was <invisible>.
75. Android FEST assertEquals(View.GONE, view.getVisibility()); assertThat(view).isGone(); expected: <8> but was: <4> Expected visibility <gone> but was <invisible>. JUNIT ANDROID FEST
76. Android FEST JUNIT ANDROID FEST assertEquals(View.VISIBLE, layout.getVisibility()); assertEquals(VERTICAL, layout.getOrientation()); assertEquals(4, layout.getChildCount()); assertEquals(SHOW_DIVIDERS_MIDDLE, layout.getShowDividers()); assertThat(layout).isVisible() .isVertical() .hasChildCount(4) .hasShowDividers(SHOW_DIVIDERS_MIDDLE);
77. Exercise
78. Spoon Automate test execution across multiple devices ! Aggregate the results ! Aggregation of screenshots http://square.github.io/spoon/
79. Spoon: screenshots Visual inspection of tests execution Spoon.screenshot(activity, "initial_state"); /* Normal test code... */ Spoon.screenshot(activity, "after_login");
80. Exercise
81. Behavior Driven Development
82. (Unit) testing in Android Android SDK (JUnit 3-based) Instrumentation tests ! !
83. Third party libraries Robotium Robolectric Mockito Fest Android Spoon
84. Cloud testing
85. A better Android emulator Automate testing ! Dozens of devices - different screen sizes - different Android versions
86. Manymo
87. Android Gradle integration
88. CI
90. Continuous integration benefits Fast feedback - fewer errors Test everything on every (nightly) build Less manual testing Regression tests without additional effort
91. Android
94. Other
95. Genymotion http://blog.genymobile.com/genymotion-jenkins-android-testing/
96. Repository manager
97. Architecture Simple architecture ! Dependency injection
98. Code quality
99. Measure...
100. Quality Tools for Android https://github.com/stephanenicolas/Quality-Tools- for-Android
101. Quality Tools for Android
102. Build pipeline tools Build (maven - gradle) Dependency repo (nexus - artifactory) Testing framework (JUnit - ...) Test coverage (Cobertura - Emma - Jacoco) Code analysis (Checkstyle, findbugs, pmd, Android Lint) Creation of deployable artifact (buildtool, artifact repo) Trigger next stage
103. Better Android apps
104. References
105. Suggested reading Android Application Testing Guide Diego Torres Milano (9781849513500) Robotium Automated Testing for Android 
 Hrushikesh Zadgaonkar (9781782168010) ! 

106. Suggested reading Test Driven Development: By Example Beck, Kent (978-0321146533) Continuous Integration: Improving 
 Software Quality and Reducing Risk 
 Duvall, Paul M. et al. (978-0321336385) Working Effectively with Legacy Code
 Feathers, Michael (978-0131177055) 

107. Suggested viewing Google IO sessions
108. Q + A
110. Contact information iDA MediaFoundry
 info@ida-mediafoundry.be
 @iDAMediaFoundry ! Filip
 filip.maelbrancke@ida-mediafoundry.be
 @fmaelbrancke ! Peter
 peter@kuterna.be
 @peterkuterna