How to build rock solid apps & keep 100m+ users happy
•
7 likes•1,901 views
The document discusses testing strategies for Android applications including acceptance testing using tools like Gwen, unit testing with JUnit and Robolectric, and strategies for structuring code in a testable way using patterns like MVP. It also covers best practices for continuous integration of tests and tools for distributed and remote testing on emulators and devices like Fork and ADB Remote to improve test execution speed.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to How to build rock solid apps & keep 100m+ users happy
Similar to How to build rock solid apps & keep 100m+ users happy (20)
Recently uploaded
Recently uploaded (20)
How to build rock solid apps & keep 100m+ users happy
- 4. Happy users Even developers?
- 7. Better code
- 9. Easy
- 10. A user walks into a bar
- 11. Doing it the test driven way Write UI test Implement Refactor Write unit test BDD TDD
- 12. Test first • Generally easier • Eliminates external dependencies • Easily repeatable
- 13. The Acceptance Tests cycle Write UI test Implement Refactor Write unit test BDD TDD
- 14. Acceptance criteria • Given: arrange • When: act • Then: assert
- 15. Example Given a user is near a music venue And the server always returns a known result When the user Shazams Then the user can check-in their discovery
- 16. gwen given(user).isNear(lexington()); given(server).returns(lustForLife()); when(user).shazams(); then(user).canCheckIn(lustForLife(), lexington()); http://github.com/shazam/gwen
- 17. Other libraries for Acceptance Tests • Instrumentation • JUnit 3 • Espresso & Robotium • Fork • HamMock Server
- 18. The Unit tests cycle Write UI test Implement Write unit Refactor test BDD TDD
- 19. What we don’t test Activities & Fragments http://github.com/xxv/android-lifecycle
- 20. What we don’t test
- 21. What we do test • Presentation logic • Business logic • That’s it
- 22. The MVP pattern Presenter Model View
- 23. The MVP pattern Presenter Model View Android
- 24. The MVP pattern • Makes presentation logic testable • No need to test “dummy” view • Avoid Android dependencies
- 25. Dependency Injection, Yourself • Breaks hardcoded dependencies • Behaviour vs Implementation • Implementations for test & runtime
- 26. Hardcoded dependencies Feature X Client Feature X
- 27. Dependency Injection Client Feature X Interface Injector
- 28. Model public interface VenueRetriever { void findClosestVenue(VenueFoundCallback callback); } public class NetworkVenueRetriever implements VenueRetriever { public void findClosestVenue(VenueFoundCallback callback) { // Some slow networking } } public class LocalVenueRetriever implements VenueRetriever { public void findClosestVenue(VenueFoundCallback callback) { // DB look-‐up / caching layer, perhaps? } }
- 29. Activity public class ResultActivity extends Activity implements ResultView { private final VenueRetriever venueRetriever; private ResultPresenter resultPresenter; public ResultActivity() { venueRetriever = venueRetriever(); } public void onCreate(Bundle savedInstanceState) { // TODO: Setup layouts & views Result result = resultToDisplay(); resultPresenter=new ResultPresenter(this, venueRetriever, result); } public void onStart() { resultPresenter.startPresenting(); } }
- 30. Presenter public class ResultPresenter { ResultPresenter(ResultView resultView, VenueRetriever venueRetriever, Result result) { public this.resultView = resultView; this.venueRetriever = venueRetriever; this.result = result; } public void startPresenting() { resultView.showResult(result); venueRetriever.findClosestVenue(new VenueFoundCallback() { public void venueFound(Venue venue) { resultView.showCheckInPrompt(venue); } }); } }
- 31. View public interface ResultView { void showResult(Result track); void showCheckInPrompt(Venue venue); }
- 32. Activity public class ResultActivity extends Activity implements ResultView { public void showResult(Result result) { //TODO show the result screen & bind result data } public void showCheckInPrompt(Venue venue) { //TODO bind the venue with check-‐in prompt view } }
- 33. Other Unit Test technologies • JUnit 4 • Robolectric java.lang.RuntimeException: Stub! • Hamcrest • JMock
- 34. Test execution
- 37. Usual execution Test Suite
- 39. Fork Test Suite http://github.com/shazam/fork
- 40. Example
- 42. Fork • Pooled execution • Infinitely scalable • Current setup 1 test / 2 seconds http://github.com/shazam/fork
- 45. If all else fails
- 46. If all else fails
- 47. If all else fails
- 48. Summary • Testing is easier than you may think • Practice, practice, practice • Toolset is limited but getting better • Ship it!
- 49. Questions?