Although you should avoid having your code tied to Android components, it's not always possible. Maybe it's Activity code, or a component that needs Context. But you still should test it.
Those tests will have to run on an emulator or a real device. They are going to be slower. But they are important nevertheless.
Here's how you can do that...
Read MoreNow we dive into unit testing.
The goal is to test a specific part of your code, just a particular class or method. That way, we can find sooner where bugs appear in your application. For that, we need to test that code in isolation, mocking all its dependencies with fake ones we can control
Read MoreA common question we get asked is why bet on Android, and why now?
Here are the 3 main reasons...
Generates fake data for testing or populating a development database. A Kotlin port of the Faker ruby gem that's suitable to use in Android development.
Read More
