Describe the bug
An issue with running cucumber tests on multiple shards. When initiating the test, max-test-shards running a false number of shards and none of them initiating the test.
Gradle build command:
:app:assembleAppDebugAndroidTest :app:assembleAppDebug -PrunCucumber
Running test:
adb shell am instrument -w -r -e debug false com.app.test/com.app.test.CucumberRunner
To Reproduce
Create a couple of cucumber tests and try to run it with flank enabling shards and using max-test-shards set to -1
Specified 4 tests but 100+ shards getting created.
Expected behavior
4 shards need to be created and tests need to run in parallel
Details (please complete the following information):
Have you tested on the latest Flank snapshot?
Yes
Post the output of flank --version.
20.09.1
Additional context
Add any other context about the problem here.
Describe the bug
An issue with running cucumber tests on multiple shards. When initiating the test,
max-test-shardsrunning a false number of shards and none of them initiating the test.Gradle build command:
:app:assembleAppDebugAndroidTest :app:assembleAppDebug -PrunCucumberRunning test:
adb shell am instrument -w -r -e debug false com.app.test/com.app.test.CucumberRunnerTo Reproduce
Create a couple of cucumber tests and try to run it with flank enabling shards and using
max-test-shardsset to -1Specified 4 tests but 100+ shards getting created.
Expected behavior
4 shards need to be created and tests need to run in parallel
Details (please complete the following information):
Yes
20.09.1
Additional context