What the numbers show
test ≥ 3 min, ≥ 40% of the job, one step ≥ 80% of test timeA single test command running in one process, or one job running every suite, means the wait grows with every test added. Split the suite across workers or jobs. Every test still runs; it just runs side by side.
The change
Shard the suite across a job matrix
strategy: matrix: shard: [1, 2, 3, 4]steps: - run: npx playwright test --shard=${{ matrix.shard }}/4Or run workers inside the job
- run: pytest -n auto # pytest-xdist- run: go test -p $(nproc) ./...- run: cargo nextest runRunner options
Verify the verdict stays the same
- 01Total tests reported after the change equals the count before.
- 02No test is marked skipped that ran before.
- 03The job's conclusion matches on the same commit.
- 04Re-run three times to catch order-dependent tests.