How to Fix Unity Batch-Mode Test Runs That Hang and Never Exit

Unity in -batchmode can still stall on a license prompt, an asset import, or a script error dialog. The right command line plus a results path makes it run and exit deterministically.

How to fix it

1. Use the test runner command line

Run with -batchmode -runTests -testPlatform PlayMode -testResults results.xml -logFile -. The -runTests path exits with a nonzero code on failure rather than hanging.

2. Avoid -quit fighting -runTests

Do not combine -quit with -runTests; the test runner manages its own exit. Adding -quit can close the editor before tests finish.

3. Stream the log and fail fast

Pass -logFile - to stream to stdout so CI shows progress, and set a job timeout so a genuinely stuck import is killed instead of burning a whole runner.

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.