Android Testing Bootstrap - DevFest Paris

Talk about android testing (at large)
DevFest Paris - 2k15
Florent NOEL & Sylvain Galand

Transcript

1. Android Testing Bootstrap with Genymotion
2. SLIDES http://goo.gl/YB4V5d Florent Noël http://bit.ly/143lDpE Sylvain Galand http://slvn.fr/+
3. Agenda 01 Context 02 What and Why? 03 How? 04 Android Tests 05 Testing with Genymotion
4. CONTEXT … why are we here today?
5. Context
6. What and Why? Hoax Buster
7. ... What & Why? Unit test Automation / UI QA Performances Environment
8. Ensures the quality of a software system Validates the requirements Part of the development cycle Often forgotten or not seriously done Definition What & Why?
9. It takes time It’s not needed Too complicated What & Why? Misconception
10. You can say: IT WORKS! Early bug is cheaper Find edge cases in your code Force to write cleaner code Because you limit the code dependency What & Why? The Truth
11. Helps Refactoring Because we love it Protects the features Make it easy, not scary Highlights the bugs What and where What & Why? Break it down
12. When and How? Good practices are good
13. “Until it is fully tested. Not complete the code is.” YODA
14. Not at the last minute Test early, often & automatically Use continuous integration Test locally before shipping code Test when it is upstream Ship with the tests written When & How? Code little Test little
15. Test Driven Development Write tests before business code We don’t do TDD For whole projects Sometimes it fits! Paralleling dev for interdependent modules Did you say TDD? When & How?
16. A bug found is a test Extend existing tests when you correct it Be serious Test should be as good as production code Some advice When & How?
17. Tests in an Android context Save a droid, write tests
18. Android Tests User Interface Business Logic Device Support What to test? According to us
19. Slower Run on device UI testing Quite Fast Run on JVM Mock framework Fast Pure JUnit Robolectric Android Test Framework Android Tests
20. Run test on the JVM Good old Java Use latest Junit Good for unit testing Android Tests Pure Junit JUnit
21. apply plugin: 'java' dependencies { … testCompile('junit:junit:4.12-beta-2') } Add the dependency Android Tests Configure module Procedure: • create a separate “pure java” module • put the Java classes under main/ • put the Junit tests under /test
22. public class CalculatorTest { protected Calculator calculator; @Before public void setUp() { calculator = new Calculator(2); } @Test public void testSumUpReturnsCorrectResult() { int result = calculator.sumUp(1); assert (result == 3); } @After public void tearDown() { //no op} } Android Tests Write tests
23. Run the gradle task from the command line. Make sure the command is run at the root of the project directory. Run all the tests for the whole project: $./gradlew test Run only the tests for the pure java module: $./gradlew :myjavamodulename:test Android Tests Run the tests
24. Run test on the JVM Run the test on the JVM Combines with a mocking framework Use the shadow objects Good for unit/integration testing Android Tests Robolectric
25. apply plugin: 'java' apply plugin: 'android-test' buildScript { repositories { jcenter() } dependencies { classpath 'com.novoda:gradle-android-test-plugin:0.10.1' } } … Add the dependency Android Tests Configure build.gradle (1/2) Apply the plugins
26. … android { projectUnderTest ':nameOfYourTheModule' } dependencies { … androidTestCompile( 'org.robolectric:robolectric:2.3') androidTestCompile( 'junit:junit:4.12-beta-2') … } Add the dependencies Android Tests Configure build.gradle (2/2) Tell the plugin which module you test
27. @RunWith(CustomRobolectricTestRunner.class) public class MainActivityRoboTest { @Test public void testWhenActivityCreatedBatteryLevelViewIsVisible() throws Exception { MainActivity activity = new MainActivity(); ActivityController.of(activity).attach().create(); int visibility = activity.findViewById(R.id.battery_level_view).getVisibility(); assertEquals(visibility, View.VISIBLE); } } Android Tests Write tests Use a custom runner
28. Run the gradle task from the command line. Make sure the command is run at the root of the project directory. Run all the tests for the whole project: $./gradlew test Run only the tests for the robolectric module: $./gradlew :myrobolecticmodulename:test Android Tests Run the tests
29. Test the UI Espresso for the win Run the test on a real device Good for integration/functional testing Android Test Framework Android Tests
30. android { defaultConfig { ... testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" } } dependencies { ... compile 'com.android.support:support-annotations:21.0.3' androidTestCompile 'com.android.support.test.espresso:espresso-core:2.0' androidTestCompile 'com.android.support.test:testing-support-lib:0.1' } Android Tests Configure build.gradle Espresso 2.0 is now part of the Android Support Library, easy integration
31. public class MainActivityEspressoTest extends ActivityInstrumentationTestCase2<MainActivity> { @Override public void setUp() throws Exception { super.setUp(); mainActivity = getActivity(); batteryLevelView = mainActivity.findViewById(R.id.battery_level_view); } public void testBatteryLevelViewIsShown() { assertOnScreen(mainActivity.getWindow().getDecorView(), batteryLevelView); } } Android Tests Write tests
32. Run the gradle task from the command line. Make sure the command is run at the root of the project directory. Make sure a device is connected to the workstation. Run all the instrumentation tests for the whole project: $./gradlew connectedAndroidTest Android Tests Run the tests
33. Android Tests Project structure - project root/ |- build.gradle |- settings.gradle |- app module |- - build.gradle |- - src/ |- - - java/ (source code) |- - - androidTest/ (espresso tests) |- robolectric module |- - build.gradle |- - src/ |- - - test/ (robolectric tests) |- core module |- - build.gradle |- - src/ |- - - main/ (source code) |- - - test/ (pure JUnit tests)
34. Android Tests How to not get INSANE dependencies { ... androidTestCompile('junit:junit:4.12-beta-2') { exclude group: 'org.hamcrest' } } packagingOptions { exclude 'META-INF/LICENSE.txt' exclude 'LICENSE.txt' exclude 'META-INF/NOTICE' exclude 'META-INF/LICENSE' } ./gradlew clean When nothing is working a good old clean is often the answer! Dealing with dependencies
35. Testing with Genymotion There is an API for that!
36. Genymotion Tools Change in orientation Change in configuration Keyboard available System language Battery life External resources Network access GPS SMS Bluetooth What to test? According to Google
37. Genymotion Tools Battery Level, mode (charging/manual) GPS Position, altitude, accuracy, bearing, ... Android ID Radio Set IMEI Java API
38. Genymotion Tools Orientation Landscape, Portrait, Angle, ... Radio Full telephony & SMS Network Simulate Wifi, 4G, 3G, Edge, … Java API Very soon
39. repositories { maven{ url "http://api.genymotion.com/repositories/releases/" } ... } Add the Java API repository Add the Java API dependency dependencies { androidTestCompile "com.genymotion.api:genymotion-api:1.0.0" } Genymotion Tools Configure build.gradle
40. buildscript { repositories { jcenter() } apply plugin: "genymotion" genymotion.devices { nexus5 { template "Google Nexus 5 - 4.4.4 - API 19 - 1080x1920" } "Nexus 7" { template "Google Nexus 7 - 4.2.2 - API 17 - 800x1280" } } Add the plugin repository Apply the gradle plugin Genymotion Tools build.gradle Define the target devices
41. Genymotion Tools Based on command line GMTool Define your devices Template, screen size, ... Customize your device Flash, Install, push, pull Start the device Before your test task Gradle Pugin Coming soon!
42. public class TestGps extends ActivityInstrumentationTestCase2<SampleActivity> { public void testGpsWarning() { //Avoid the test if not a Genymotion device if (!GenymotionManager.isGenymotionDevice()) return; GenymotionManager.getGenymotionManager(context) .getGps() .setLatitude(64.13367829) .setLongitude(-21.8964386); //Your tests assertEquals(view.getVisibility(), View.GONE); } Test if Genymotion device Set the GPS Position Genymotion Tools TestGPS.java Test your app there! Let’s go to Dalvik
43. "Nexus 10" { template "Google Nexus 10 - 4.3 - API 18 - 2560x1600" density "XHDPI" width 800 height 600 virtualKeyboard true flash "PATH_TO/test.zip" install "PATH_TO/test.apk" pushBefore ["PATH_TO/test.txt", "PATH_TO/test2.txt"] pullAfter ["/system/build.prop":"PATH_TO/res/"] logcat "PATH_TO/res/Nexus 10.logcat" stopWhenFinish false deleteWhenFinish false ... } Edit the device on the fly Override /system/ Genymotion Tools build.gradle push/pull files before/after tests Install apps Route logcat to a file And more!
44. Test samples https://github.com/flo-genymobile/JustTestIt Genymotion Java API sample https://github.com/Genymobile/genymotion-binocle Genymotion Gradle plugin sample Coming soon What to test, according to Google http://developer.android.com/tools/testing/what_to_test.html References & Links
45. Florent http://bit.ly/143lDpE Thank you! Sylvain http://slvn.fr/+ SLIDES http://goo.gl/YB4V5d