Parameterized Instrumented tests mangle test output

E.g. Android Studio displays them as:

Note that the parameterized test method and its cases seem to have been put under new mangled class headings (“String)”) instead of all grouped under the test class (StupidConnectedTest). Additionally, the parameter cases (“”, “abc”, “123”) have been mangled with the method name appended.

Checking the console output reveals the parameterized test has been similarly mangled there too, so this is not or not solely an IDE issue:

gradle_instrumentation_param_tests_output.txt

Sample instrumentation test file (src/androidTest/java/stupidSampleGradleProject/):

StupidConnectedTest.java.txt

Sample build.gradle: build.gradle.txt

[mannodermaus]

Released in 1.2.0!

[mannodermaus]

The lack of intermediate nesting is indeed attributable to a limitation with how the Android instrumentation seems to report parameterized tests. Keeping in mind that instrumentation test support is banking on the existing infrastructure, which has to map the new stuff to JUnit 4, it’s an unfortunate consequence that nesting can’t be done arbitrarily - there’s only class nodes and their direct children, the test methods.

As an alternative to the current approach, I considered making each dynamic test group its own entry on the class level (i.e. there would be JavaInstrumentationTests & JavaInstrumentationTests.testParameterized() on the same level in the hierarchy). Ultimately, I decided against that, though.