Web and Mobile
Friday, 12. May 2017., 10:25
Android developer walks into a bar, runs his test suite, orders a couple of drinks, relaxes, meets new people, gets drunk, goes home, passes out on the couch and the tests fail.Although we’ve seen some significant improvements recently, we’re still not there yet when it comes to automated tests in Android - running tests on the emulator is slow, decoupling from the framework is not easy, TDD is practically not possible (or is it?). This talk will explore ways to improve the situation.We'll cover available tools and proposed approaches to testing on Android. Then we'll go through recommended practices for testing our code and see how it aligns with Android. Finally we will try to propose a maintainable approach to writing tests on Android with regards to (and examples of) unit testing, UI testing and how to test some complex use cases specific for native mobile applications.Buzzwords you will hear in this talk: UI tests, unit tests, dependency injection, mocks and stubs, TDD, immutability, side effects, pure functions, state, testable architecture, boundaries, JUnit, Mockito, Espresso, RxJava, test coverage.