You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on making changes so this works but so far, still only seeing the tests for debug variant running.
I changed the AffectedTestConfiguration to:
open class AffectedTestConfiguration {
var variantToTest : String = "debug"
var assembleAndroidTestTask : String? = "assemble${variantToTest.capitalize()}AndroidTest"
var runAndroidTestTask : String? = "connected${variantToTest.capitalize()}AndroidTest"
var jvmTestTask : String? = "test${variantToTest.capitalize()}UnitTest"
companion object {
const val name = "affectedTestConfiguration"
}
}
Any pointers? Would love to make a PR with the fix.
The text was updated successfully, but these errors were encountered:
Hi @michaelcarrano - oops, looks like the documentation and sample slipped with actual usage. I'll fix that shortly.
You should be able to use assembleAndroidTestTask, runAndroidTestTask and jvmTestTask to specify which tasks you want to run when the tests run for the given module.
I am playing around with this plugin and it seems like the
variantToTest
that is mentioned in the README isn't actually implemented.You can see
variantToTest
isn't defined in AffectedTestConfiguration. However, you can see an example of this in the sample app AffectedTasksPluginTo reproduce, you can try adding
variantToTest
in one of the sample/build.gradle files such as https://github.com/dropbox/AffectedModuleDetector/blob/main/sample/sample-app/build.gradle#L8-L10. I actually run into a compile error when I try to build after addingvariantToTest
.I am working on making changes so this works but so far, still only seeing the tests for debug variant running.
I changed the
AffectedTestConfiguration
to:Any pointers? Would love to make a PR with the fix.
The text was updated successfully, but these errors were encountered: