David Carver

The other option you have is a custom resolution strategy to exclude the particular items you don't want to bring down.

Recently experienced this with 4.5.1... same tests run fine with 4.3. During the Application startup, we have an custom analytics that gets initialized on a background thread. The code here...

@es0329 I extracted the DSL into it's own .gradle file, and include it as part of the scripts that need to use it.

I did eventually, move the source code to build locally as part of the buildSrc directory, but in general I kept the configuration as a standard gradle option. In the...

I'm seeing this as well on Java 11.

There is a work around for Mockk issue documented here: https://github.com/mockk/mockk/issues/480

Which coverage plugin are you using in Android Studio? It comes with two built in. IntelliJ's coverage, and Jacoco. I've seen tests have issues with IntelliJs's coverage plugin, you can...

https://www.jetbrains.com/help/idea/configuring-code-coverage-measurement.html While the above link is for IntelliJ, the code coverage options in Android Studio 2.3 were in the same place. Jacoco should be one of the options.

@esyd1pi0 does this happen in Android Studio or at the command prompt? Certain versions of gradle and jacoco aren't compatible. If you are using the latest versions of gradle you...

The problem is the the sharedTest module, doesn't actually work in a lot of cases. The IDE handled it fine before and it is a standard gradle feature to be...