Closed artem-zinnatullin closed 6 years ago
I am seeing issues with the gradle plugin. works fine until I specify more than one K/V pair.
If I specify one K/V pair I get:
Args(appApkPath=[...] testApkPath=[...], testPackage=[...], testRunner=[...], shard=true, outputDirectory=[...], instrumentationArguments=[(notAnnotation com.trevjonez.kontrast.KontrastTest, )], verboseOutput=true, devices=[], devicePattern=)
With a second arg added:
Args(appApkPath=[...], testApkPath=[...], testPackage=[...], testRunner=[...], shard=true, outputDirectory=[...], instrumentationArguments=[(notAnnotation com.trevjonez.kontrast.KontrastTest screenshotsDisabled false, )], verboseOutput=true, devices=[], devicePattern=)
Plugin assembled them as the readme instructs --instrumentation-arguments key1 value1 key2 value2
which can be seen here.
I suspect the solution to this issue would solve mine as well? I am hanging forever at Starting tests...
when I have more than one K/V pair I suspect it is like you say 'am instrument' prints it's help manual and Composer then does nothing until timeout occurs.
If I try to run Composer with following arguments:
It'll form following internal representation for
instrumentationArguments
:Which then forms wrong set of arguments for
adb shell am instrument
andam instrument
prints it's help manual and Composer then does nothing until timeout occurs.If I pass this arguments in same form to
adb shell am instrument -w -e class Class1#test1,Class2#test1
it'll work fine and run only these particular tests.instrumentation.output
: