Voting: Which is your favourite way to support robolectric? about android-gradle-template HOT 5 CLOSED

https://github.com/robolectric/robolectric-gradle-plugin is probably the preferred solution at this point, as it's being updated by the robolectric team.

from android-gradle-template.

it should be the best solution. it will never be a solution for me until we have a workaround following issues.

1. with that plugin we have some issues when we combined robolectric and espresso which is tracked here robolectric/robolectric-gradle-plugin#17
2. it is hard to get robolectric tests running inside android studio, documented at https://github.com/robolectric/deckard-gradle

from android-gradle-template.

My problem with robolectric-gradle-plugin is that it uses androidTest sourceset, preventing a clean separation between unit and functional tests (e.g. Espresso). This is a complete deal-breaker for me as functional tests can be very useful for testing parts of the app that would be overly complex using Robolectric.

My preferred way of using Robolectric is having unit-tests in a separate gradle module using the standard java plugin (allowing functional tests and unit tests to work).

from android-gradle-template.

Looks like we need no plugins anymore. With the new experimental unit test feature we can easy use robolectric. See the example https://github.com/nenick/AndroidStudioAndRobolectric or read a step by step guide http://nenick-android.blogspot.de/2015/02/android-studio-110-beta-4-and.html

from android-gradle-template.

It is possible to use robolectric without extra plugins but having the possibility to use separated test modules is still essential for me. Another advantage I have all sources anytime in Android Studio instead of switching between unit and android tests.

jcandksolution robolectric plugin is now deprecated and replaced by native unit test support.

So I switched this template back to his original root.

from android-gradle-template.