Kover doesn't follow the configured "testBuildType" for an android project.

[gerardoepitacio]

Having the example project in the branch multiple_android_flavor

https://github.com/gerardoepitacio/KoverTest/tree/feature/multiple_android_flavor

when I try to execute the task:

./gradlew :app:koverHtmlReport

throws the following error

> Task :app:compileAppQaUnitTestKotlin FAILED
e: /Users/ge/dev-test/KoverTest/app/src/test/java/com/example/koverfail04/RemoteDataProviderImplTest.kt: (8, 50): Unresolved reference: RemoteDataProviderBuilder

This is because, Kover tries to build the build type "qa", which can't reach the resource of the build type "development"

even though "testBuildType" was correctly configured in android {... } to explicitly run my test for the development build type.

Additional information about changing the test build type

Change the test build type
https://developer.android.com/studio/build/gradle-tips#change-the-test-build-type

Expected behavior, one of the following scenarios might be good to follow.

• Kover should be able to follow the configured testBuildType, and compile only the required resources to run the tests in the configured build type.
• Kover should generate different tasks for every build type and product flavor, to be able to generate reports for specific build type and product flavor (more recommended.).

[shanshin]

Relates #78

[shanshin]

Hi,
in the current version Kover does not support working with build types and flavours.

[gerardoeg]

There is a way to help to support the expected behavior for this Issue?.

@shanshin

[shanshin]

@gerardoeg, hi, thank you for the offer.
This feature is already being developed and will most likely be included in the next big release (0.7.0 or 0.8.0).

[shanshin]

Duplicates #18