soak-test

A soak test detects memory leaks and stability regressions by running structured, extended play sessions with timed checkpoints. You generate a protocol specifying exactly what to record at 30m, 1h, 2h, and 4h intervals to capture slow performance drift.

Yes, the soak test protocol includes engine-specific monitoring guidance with concrete measurement items and alert thresholds for Godot, Unity, and Unreal to accurately track memory leaks and performance drift during extended sessions.

The best way to log gameplay fatigue and performance drift is using a checkpoint-based protocol that specifies exactly what to record at timed intervals. This produces a markdown QA artifact with baseline metrics and post-session analysis for triage.

You need a structured soak test protocol during Polish and Release phases, for regression soaks after fixes, or when extended session behavior is not yet characterized. It uncovers slow memory leaks and player fatigue that only appear during long sessions.

You create a QA tracking artifact by generating a markdown output file containing baseline metrics, checkpoint logs, post-session analysis, and an issues table. This file is prepared automatically for triage and release gate checks.

Yes, you can use the soak test protocol for regression soaks after fixes. It applies to game projects during Polish and Release phases to verify that memory leaks, stability regressions, and performance drift have been resolved.