Develop Reference

NoClassDefFoundError when running unit test with Gradle task

I have a project using dynamic feature module, and I want to run my unit test in feature module via gradle task (for my CI purpose):
./gradlew :feature_product:test
But it always gives me NoClassDefFoundError for tests that have dependencies on classes from the base module:
com.example.android.feature.product.ProductViewTest > on vote change to negative FAILED
java.lang.NoClassDefFoundError: app.BaseView
ProductView class from the feature module extends BaseView from the base module.
Oddly, it succeeds when run in Android Studio, it works fine.
Then I notice something different in the logs, when I run via command line and when I run Android Studio. The first line in the Android Studio is generateDebugSources, something which absent when I run ./gradlew test
Executing tasks: [:lib_ui:generateDebugSources, ...]
How do I fix this? Does Android Studio has different command with the provided command ./gradlew test when I press Ctrl+Shift+R ?

After searching further about this issue, I found it also being reported in the android-test and app-bundle-samples projects and there is also an issue in the issue tracker.
It turns out this issue fixed in the Android Gradle Plugin 4.1.0 as per comment in the issue tracker.
If you don't want to update AGP to 4.1.0 which is still in alpha, adding this to the feature module's build.gradle fixed the issue for me, as per this comment:
testRuntimeOnly(files("$projectDir/../b_app/build/intermediates/app_classes/debug/classes.jar"))

If it is a missing task that you believe is necessary then calling it first like below should do the trick:
./gradlew :lib_ui:generateDebugSources :feature_product:test
I would even go full on and assemble the dependencies if necessary though that might take more time:
./gradlew :lib_ui:assemble :feature_product:assemble :feature_product:test

Generating Code Coverage Report with Android Studio 1.0

I'm trying to generate a Code Coverage report using Android Studio and the gradle plugin.
I've done alot of research and seem to have found that using the jacoco plugin is the way to do it. I currently only have instrumentation and junit tests which I run with the gradle wrapper using gradle 1.13 that I execute with ./gradlew connectedCheck.
The appropriate part of my gradle file looks like this:
mock.initWith(debug)
mock {
testCoverageEnabled true
}
Upon doing so it generates a coverage.ec file that I have no idea what to do with. Apparently you need a coverage.em file for emma to compile it but I'm not sure where to generate that.
I've also tried this without a gradle wrapper using gradle 2.2.1
According to http://gradle.org/docs/current/userguide/jacoco_plugin.html#jacoco-application-output it should be generating an html file with the coverage report in it but I am unable to do so. Does anyone have any great tutorials or a way to use the coverage.ec file?

Android: project set up for unit and functional tests

I'm trying to incorporate more unit tests, specifically Robolectric test into my project. Right now I already have some functional test that are in my androidTest package. The problem is that if I add a Robolectric Test Class to that package then when I execute ./gradlew test all the functional test are ran along with the Robolectric/Unit Tests.
Is best practice to be using a different test package for my unit tests? And if that's the case then will I have to configure the Gradle test task to look at only the unit test package?
I should mention that I'm on Android Studio 1.0, Gradle 1.0, and Robolectric 2.4.

./gradle test runs all the test in your project. You will likely have (at least) two modules in your project, lets call them app and robolectric-tests.
You can tell Gradle to run a task on a specific module by using ./gradlew :module:task. So in your case, you could run ./gradlew :robolectric-tests:test to run only your Robolectric tests.

Android gradle build that code coverage for robolectric tests

Is there a way to to have a gradle build that will generate code coverage from robolectric test that can be sent to sonar?

As far as I can tell: At this time, No.
In order to have code coverage you need Emma support and that's not yet fixed in the android gradle build plugin. It's supposed to come in version 0.8.+ but it was also "supposed" to come in version 0.6+ so don't hold your breath.
Roadmap: http://tools.android.com/tech-docs/new-build-system/roadmap
Related Emma Issue: https://code.google.com/p/android/issues/detail?id=60964

Android Gradle two instrumentation test suites

I am trying to set up a second instrumentation test suite for an android project. The project builds under Gradle and the ADT plugin.
I have instrumentationTestSuiteA and instrumentationTestSuiteBand buildTypeAand buildTypeB.
I would like instrumentationTestSuiteA to run on buildTypeA, and instrumentationTestSuiteB on buildTypeB.
How could I accomplish this?