Code coverage? about robolectric-gradle-plugin HOT 5 CLOSED

i never tried jacoco within this plugin, but successful with a different plugin to enable robolectric tests. The difference is just a separated robolectric module. so it should be possible to archive the same here. Here is an example https://github.com/nenick/android-gradle-template and here the most magic part to enable jacoco https://github.com/nenick/android-gradle-template/blob/master/Scripts/jacoco-support.gradle

from robolectric-gradle-plugin.

@tommyd3mdi @nenick http://chrisjenx.com/gradle-robolectric-jacoco-dagger/ I wrote a blog about it.

from robolectric-gradle-plugin.

Thanks, I've stumbled upon this one in the meantime as well. I also just figured out that the basic instrumentation tests also already run into the Jacoco/Dagger incompatibility described here: https://code.google.com/p/android/issues/detail?id=69174 and since the majority of my tests are instrumentation tests your described workaround is of little use for my (few) robolectric-driven tests.

from robolectric-gradle-plugin.

nice blog article, looks like i know from where some line comes from ;)

solution to include dagger was also discussed here nenick/android-gradle-template#5 but fixing the names looks better than exclude the generated files.

you are still trying coveralls integration? When you need some help https://github.com/nenick/android-gradle-template has already coveralls integration

from robolectric-gradle-plugin.

@nenick I sent a PR to fix Coveralls plugin, 0.5.x uses the android plugin an natively includes the main source.

I based my work off yours, but I didn't like robolectric being a separate java module.

Thankfully google have added Unit Testing as a higher level priority eventually we can forget these silly hacks.

from robolectric-gradle-plugin.