`˛gradlew testDebugUnitTest` is not picking up tests from `:app` module since I have flavors, what g...

# gradle

[ursus]

˛gradlew testDebugUnitTest is not picking up tests from :app module since I have flavors, what gives? Wasnt it supposed to run everything?

[gildor]

We register alias task for default flavor:

tasks.register("testDebugUnitTest") {
        dependsOn("testFlavornameDebugUnitTest")
}

[ursus]

yea im about to do that, but stupid thing is that clean etc work, since its the same name

[ursus]

thx

[ursus]

why does gradlew test work though?

[gildor]

clean task available by default in all modules, it lifecycle task, which used as hook for all other cleanup tasks

But I don't want to say that existing behavior of AGP is good. I would prefer if standard lifecycle task test would work for all flavors, but it causes a lot of questions how it should work for flavors, flavor may change test input, so I think this why it works like that. But on practice it usually fine to run tests for some default flavor

[gildor]

Test works because it default lifecycle task, version with UnitTest is a task generated by AGP

[ursus]

yea, I thought testDebugUnitTest was that, I only now realized it wasnt running the top level module tests, smh

[gildor]

Yeah, it doesn't exist if flavors are used