soak-test

To create a soak test protocol, you can generate a structured markdown file with timed checkpoints tailored to your chosen duration and focus, such as memory, stability, or balance. It reads project documentation to contextualize the protocol.

A soak test is used to observe and log long play session metrics to uncover memory leaks, performance drift, and player fatigue that only appear over time during extended play testing in Polish and Release phases.

You can set up memory and stability checkpoints by defining timed intervals within the generated soak test protocol. The protocol structures these checkpoints based on your chosen duration and focus areas.

Yes, the soak test protocol provides engine-specific monitoring guidance for Godot, Unity, and Unreal to help you track metrics during your extended play testing sessions.

No, the generated soak test protocol does not execute the test itself. It outputs a structured markdown file defining timed checkpoints and monitoring guidance for you to follow during the play session.

You should run a soak test during the Polish and Release phases, or for regression testing after stability fixes, to observe long-duration play metrics and uncover memory leaks or balance issues.