test runner under `--shard <shard>`

[himself65]

What is the problem this feature will solve?

We use the nodejs test runner in CI because it has the same environment(pure node.js) as the production.

But I found that the single CI running test case needs to be faster because we have many server unit tests.

If shared could be supported, it would reduce the CI runtime because of multi runners.

What is the feature you are proposing to solve the problem?

# In different CI runner
node --test --shard=1/5
node --test --shard=2/5
node --test --shard=3/5
node --test --shard=4/5
node --test --shard=5/5

Other test libraries also support this feature:

• https://vitest.dev/guide/cli.html#shard
• https://playwright.dev/docs/api/class-testconfig#test-config-shard

What alternatives have you considered?

Currently, I have to split the tests into different folders manually.