Hi! I have an Android project where

testDebugUnitTest

is not running unit tests in most of our application modules, i.e.

com.android.application

ones. It happily runs them in all the library modules, and curiously, one sample app module. More specific tasks like

testMyProductVariantDebugUnitTest

do run them. What can I look at (logs etc) to understand why this is happening?

better ask #CJYS1DAP5 or in an Android community but it depends on how your build variants are set up, that's expected

> it depends on how your build variants are set up, that's expected Can you expand on this please?

your app module doesn't have an "testDebugUnitTest", because only variants "test${Variant}DebugUnitTest" for various variants exists

Hmm. Thank you for this. So, the rationale makes sense. But if I iterate through the variants, I find that in their properties,

unitTestEnabled

is already true. So enabling it (and I have) doesn't do anything different. I suppose the answer might be a classic 'dependsOn' relationship?

no, I mean that you should use the existing lifecycle task "test"

Oh, you're saying run

test

rather than

testDebugUnitTest

and then disable a bunch of stuff via

enableUnitTest = false

?

yes

Yeah, that makes a lot of sense, cheers. I suppose we historically ran the 'debug' task version to avoid pointlessly running the test suite again for all modules'

release

variants, but I don't know if that does actually happen or not, and similarly to avoid repetition for all product variants which as you say we could easily prevent in one coherent place.