Unit Testing in Android

A talk on Unit Testing in Android Delhi Meetup held in Gojek, Gurugram covering up basic concepts of Unit Testing, annotations, frameworks and how to write testable code

Session Link : https://www.youtube.com/watch?v=0K4S3vkulGc&t=8s&ab_channel=ADG-Delhi

Transcript

1. Unit Testing in Android Anuj Middha Niharika Arora ADG Delhi Senior Software Engineer,1mg
2. Agenda • Introduction to App Architecture and Unit Tests • Tools and Frameworks • Writing Testable Code • Demo
3. Good/Clean Code Base? What is that?Why should we have good/clean code base?
4. Scalable | Stable | Testable | Modular
5. Application Architecture Why do I care?
6. MV* Patterns MV (C | P | VM) 1. Data source of the application 2. Network layer, database operations Model
7. MV* Patterns MV (C | P | VM) Responsible for displaying data View
8. MV* Patterns MV (C | P | VM) Controller manipulates, edit, uses data model and show it to users via View. In Android, Activity/Fragments can act as both View and Controller Controller
9. MV* Patterns MV (C | P | VM) Presenter is a simple java class that do not contain any UI components, it just manipulates data from model and display in on View. Presenter
10. MV* Patterns MV (C | P | VM) They provide data and functionality to be used by views. They are what define the structure and behavior of the actual application you are building ** Many View can be mapped to one View-Model ViewModel
11. MVC vs MVP vs MVVM Which one to follow?
12. Activity/Fragment/View should be Business logic free
13. Unit Test “ A software testing method by which individual units of code, are tested to determine whether they are fit for use. The smallest testable part of an application (Classes and Methods).
14. Anatomy of a unit test ▪ Arrange all necessary preconditions and inputs. ▪ Act on the object or method under test. ▪ Assert that the expected results have occurred.
15. Benefits of a unit test ▪ Find problems early. ▪ Facilitate refactoring. ▪ Simplify integration. ▪ Document code usage.
16. Types of Android unit test ▪ Instrumented unit test ▪ Local unit test
17. Instrumented unit test ▪ Runs on device or emulator ▪ Actually affects the device
18. Local unit test ▪ Runs on JVM ▪ No need for device or emulator ▪ Faster than instrumented unit test
19. Android Unit Testing Tools & Framework • JUnit • Mockito • PowerMock • Robolectric • Espresso • UI Automator
20. JUnit Gradle - testImplementation 'junit:junit:4.12'
21. JUnit Annotations @Test @Before @After @BeforeClass @AfterClass @Ignore
22. JUnit statement assertions assertFalse(condition) assertEquals(expected, actual, tolerance) assertNull(object) assertNotNull(object) assertSame(expected, actual)
23. Mockito “ Objects pre-programmed with expectations which form a specification of the calls they are expected to receive.
24. Mocking reasons Reason - Your Object have external dependencies Mockito is a Java framework allowing the creation of test mock objects in automated unit tests dependencies { testImplementation "org.mockito:mockito-core:2.11.0" }
25. Mockito features ▪ Mocking ▪ Stubbing ▪ Argument matchers ▪ Verifying number of invocations ▪ Verifying order of invocations
26. Mockito limitations ▪ Cannot mock final classes ▪ Cannot mock static methods ▪ Cannot mock final methods ▪ Cannot mock equals(), hashCode()
27. PowerMock PowerMock is a framework that extends other mock libraries such as Mockito with more powerful capabilities. Enable mocking of static methods, constructors, final classes and methods, private methods, removal of static initializers and more.
28. PowerMock testImplementation 'org.powermock:powermock-module-junit4:1.6.4' testImplementation 'org.powermock:powermock-module-junit4-rule:1.6.4' testImplementation 'org.powermock:powermock-api-mockito:1.6.4' testImplementation 'org.powermock:powermock-classloading-xstream:1.6.4'
29. Robolectric Unit Testing framework which allows Android application to be tested on JVM without an emulator or device. Robolectric provides implementation of Android SDKs by rewriting Android core libraries using shadow classes
30. Robolectric Gradle - testImplementation “org.robolectric:robolectric:latestVersion” Robolectric handles inflation of views, resource loading, and lots of other stuff that’s implemented in native C code on Android devices. **Robolectric is not an integration test framework, i.e., you cannot not test the interaction of Android components with it.
31. Writing Testable Code Or how not to lose your mind coding
32. Writing Tests can be hard!
33. When done right, results in a clean, easy to maintain codebase
34. Good Unit Test • Easy to write • Readable • Reliable • Fast • Truly Unit
36. Testable Code
37. Deterministic
41. Can you guess why this code is non deterministic?
42. Side Effects
44. Solution?
45. Higher order functions
47. Rule of Thumb • Write deterministic code • Minimize side effects • In essence, write pure functions Can impurity really be removed? • As much as possible, extract it out and keep it contained
48. Red Flags • Static properties and Fields
49. Red Flags • Singletons
50. Red Flags • Static Methods
51. What is TDD Test-driven development (TDD) is an approach for software development where you write tests first, then use those tests to drive the design and development of your software application.
52. TDD Cycle Red — think about what you want to develop Green — think about how to make your tests pass Refactor — think about how to improve your existing implementation
53. DEMO
54. References Github Link - https://github.com/Niharika8059/UnitTesting-MVVM-Kotlin-Coroutines- Sample Medium link - https://medium.com/1mgofficial/unit-testing-in-mvvm-kotlin-databinding -ba3d4ea08f0e
55. Resources https://semaphoreci.com/community/tutorials/stubbing-and-mocking-with-moc kito-2-and-junit https://android.jlelse.eu/better-testing-with-mvvm-ae74d4d872bd https://medium.com/mindorks/unit-testing-for-viewmodel-19f4d76b20d4
56. “Writing a test is simple, but writing a code that can be tested is not so simple”
57. QUESTIONS?