Espresso's consistency makes it really easy to learn.
Want to match a view with a specific id? Use
withId(R.id.some_id). Need to match with a piece of text? Use
withText("some text). Awesome, consistent and it's very clear what it is you are doing.
After a few hours writing test code you'll find your code being a little bit too verbose. Not anymore.
Why should you need to explicitly specify that you are matching with some text if you are passing in some text as a parameter? Some for the view id, you can already see that it is a view id.
Ristretto allows you to write the same test code as you already write, but less verbose.
Simple class created in order to make Android automation testing easier, faster, cleaner and more intuitive. It synchronizes operations that might occur on any thread - with test thread. ConditionWatcher can be used as a replacement to Espresso's IdlingResources or it can work in parallel with them.
Selendroid is a test automation framework which drives of the UI of Android native and hybrid applications (apps) and the mobile web with Selendroid. Tests are written using the Selenium 2 client API and for testing the application under test must not be modified.
Selendroid can be used on emulators and real devices and can be integrated as a node into the Selenium Grid for scaling and parallel testing.
A sample android starter project to demonstrate the integration of the following tools:
The goal of this project is to speed up the setup of Robolectric, Robotuim, Roboguice, and Mockito in Android Studio. Since there is not built in support for Robolectric there is a lot of manual set up that has to be done. This project uses Robolectric-gralde plugin as well as his InjectedTestRunner.