Add --shard option

[andrewvc]

Users may want to distribute work across multiple machines (either with or without heartbeat). In that scenario they would only want to execute a subset of tests on each machine.

This issue proposes adding a --shard=M:N option, where M is the shard number, and N is the total number of shards. Given two machines running the same suite users would invoke synthetics with --shard=1:2 and --shard:2:2 based on hashes of the journey names.

[paulb-elastic]

Do you think this is still needed (a sharding specific strategy) now that we support filtering and tags that can be used to control what’s run? I know it’s not exactly the same, but do they provide enough flexibility for the use case?

[andrewvc]

Maybe? Can we revisit in a month? It might be useful for a service.

…

On Thu, Sep 9, 2021 at 3:14 AM Paul Bianciardi ***@***.***> wrote: Do you think this is still needed (a sharding specific strategy) now that we support filtering and tags that can be used to control what’s run? I know it’s not exactly the same, but do they provide enough flexibility for the use case? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#277 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABACY6EXCQ2AARZLQG4WKDUBBUGVANCNFSM443AGIAA> .

[vigneshshanmugam]

Guess we can do this once we migrate to PW test at some point which would come as free as it can be done using PW test framework. https://playwright.dev/docs/test-parallel/#shard-tests-between-multiple-machines