Android Testing: An Overview
12 likes3,416 views
This document provides an overview of testing Android applications. It discusses using Robolectric to run tests on a development machine without needing an emulator. It also recommends libraries like Hamcrest, FEST Android, and Awaitility to improve testing. Spoon is presented as a tool to take screenshots during tests. Continuous integration with Jenkins and generating test reports and documentation are also covered.
Android Testing: An Overview
- 1. An Overview of Android Testing Eric Oestrich BohConf 7/19/2013
- 3. You can test Android?
- 4. Regular Android testing leaves a lot to be desired
- 6. Run tests on your development machine
- 7. JUnit 4
- 10. Eclipse Should just use IntelliJ
- 11. Android Studio Uses gradle, not much support for this yet
- 12. Downsides
- 13. Content Providers are still hard to test
- 14. Still somewhat new Not every area is able to be tested nicely
- 16. Extra Libraries You Should Consider
- 18. Hamcrest ● Nicer assertions than regular JUnit
- 21. FEST Android ● Fluent assertions make test read nicely ● FEST additions specific to Android
- 22. FEST Android assertThat(view.getVisibility(), equalTo(View.GONE)); vs assertThat(view).isGone();
- 24. Awaitility ● Handles testing asynchronous code nicely ● Set timeouts
- 25. Awaitility public void testActivityTitle() { await().atMost(TIMEOUT_SECONDS, TimeUnit.SECONDS).until( activityTitle(), equalTo("Notification")); Spoon.screenshot(getActivity(), "activity_title"); }
- 26. Awaitility protected Callable<String> activityTitle() { return new Callable<String>() { @Override public String call() throws Exception { return mActivity.getTitle().toString(); } }; }
- 28. Spoon ● Take screenshots of app during test ● Compiles to animated gif ● Instrumentation tests
- 29. Spoon public void testActivity() { Spoon.screenshot(getActivity(), "activity"); }
- 32. Jenkins Shell Script export ANDROID_HOME=/var/lib/jenkins/tools/android-sdk mvn clean test --batch-mode
- 33. Javadocs
- 34. JUnit Results