Now that you know what your mobile application will do and look like, it’s time to get your various environments set up. Here’s our list of things we check off at Collective Idea for creating an Android app.
Developing a mobile application that works on both iOS and Android takes a bit of work. Here are some best practices to get you going.
You don’t need an
sleep() is fickle. Make Espresso wait for your observables running on background schedulers with this one cool trick!
When we stub an intent, we are able to intercept it so the intent is never sent to the system, and specify how it should respond. This can be helpful in your Android tests when you need to know if an intent was sent, but you don’t actually need the Activity to start. This can be accomplished by using espresso-intents.
Using espresso-intents for testing Android Activity Intents