Instrumentation tests with ANDROIDX_TEST_ORCHESTRATOR
: Parameterized tests give issues
#337
Labels
ANDROIDX_TEST_ORCHESTRATOR
: Parameterized tests give issues
#337
I have two issues to report when running instrumentation tests while using the Android Test Orchestrator. Feel free to tell me to split these up into two issues - happy to do so!
I've repeatedly tested this with version
1.10.0.0
and1.10.2.0-SNAPSHOT
of the plugin.If I disable the Android Test Orchestrator (by simply commenting out
execution = "ANDROIDX_TEST_ORCHESTRATOR"
), it all behaves as it should - exactly as the local tests do.While the Wiki says to use
@UseTechnicalNames
, I've not needed it so far. Annotating the test class with that does not resolve the issues reported here.Test Class
Works: Local Test
When running the tests for that whole class as a local test, the following is displayed in Android Studio:
It also works when executing all tests for the whole package, or individual test methods.
Fails: Run Class/Package As Instrumentation Test
However, if we run that same class (renamed to
MyTest
in the screenshot below) or the whole package its in as an instrumentation test, we first get no results at all:If we check logcat, we can find this:
Note: We see a similar exception in logcat when we change one of the test methods to take a
String
together with@ValueSource
. It will then sayInvalid test class 'java.lang.String'
instead.Kinda Works: Wrong Names When Running Method
If we however run each test individually, it works, although the names are not as expected:
The text was updated successfully, but these errors were encountered: