Quick answer: Split the suite into independent shards run on parallel runners, and eliminate shared mutable state so tests are safe to run concurrently.
A serial suite is the wall-clock bottleneck once you have thousands of tests. Sharding across runners cuts the time, but only after tests are independent.
How to fix it
1. Shard across runners
Partition tests into N groups and run each group on its own CI runner in parallel, then aggregate results. Wall-clock time drops roughly by the number of shards.
2. Remove shared mutable state
Before parallelizing, isolate singletons, static fields, and shared files so two tests running at once cannot corrupt each other. Parallelism exposes every hidden coupling.
3. Balance the shards
Split by historical test duration rather than count so each shard finishes around the same time, instead of one slow shard gating the whole run.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.