[Feature request] Running tests from a shard in a single instrumentation

[edamyanov]

In Spoon 2.x every test is run in a separate instrumentation call. When using sharding this has increased significantly the time for which tests are executed. Recently --single-instrumentation-call flag has been added but it runs all tests in a single instrumentation. I could not find an option to run only tests from a particular shard in a single instrumentation call.
Have you considered adding such an option so that only tests from a particular shard to be executed in a single instrumentation call (as it used to be with Spoon 1.x)?

[JakeWharton]

Sounds good. Want to send a PR?

…

On Fri, Jan 5, 2018 at 10:02 AM Emanuil Damyanov ***@***.***> wrote: In Spoon 2.x every test is run in a separate instrumentation call. When using sharding this has increased significantly the time for which tests are executed. Recently --single-instrumentation-call flag has been added but it runs all tests in a single instrumentation. I could not find an option to run only tests from a particular shard in a single instrumentation call. Have you considered adding such an option so that only tests from a particular shard to be executed in a single instrumentation call (as it used to be with Spoon 1.x)? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#509>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEEETFY2GxPSjcKCiqYioFOp6knDMKIks5tHjmLgaJpZM4RUjAE> .

[edamyanov]

Yes, with pleasure!

[edamyanov]

I created a PR for this issue but as I see @tchernykh has made another :)

[jaredsburrows]

@edamyanov Will this solve the problem?

• with out specifying singleInstrumentationCall = true - all reports are clobbered
• specifying singleInstrumentationCall = true - no reports

[edamyanov]

@jaredsburrows Unfortunately not but I will take a look if I can fix it.

[edenman]

Should be fixed, lmk if not