soak-test

A soak testing protocol detects late-cycle failures like memory leaks by generating timed observation checkpoints for extended play sessions. You run the skill to produce a ready-to-fill QA document with duration-appropriate intervals to log issues consistently.

Tracking stability regressions during playtests requires a duration-based checkpoint protocol with intervals like 30m, 1h, 2h, and 4h. This ensures performance drift and stability failures are logged at consistent intervals alongside baseline metrics and post-session trend analysis.

Yes, the soak test protocol provides engine-aware measurement guidance for Unity, Unreal, and Godot. This ensures results for memory leaks and performance drift are captured using the correct engine-specific monitoring metrics during the extended play session.

Fun-fatigue regressions are measured using focused observation modes within the soak test protocol. By selecting the balance and fatigue mode, testers manually follow a checklist to record gameplay issues at timed checkpoints throughout the extended session.

Run a soak test during the Polish and Release readiness phases, after standard regressions are resolved. It is specifically applied when extended play risks like memory leaks, stability failures, and fatigue issues have not been formally tracked.

Yes, you can target specific risks by using focused observation modes for memory, stability, or balance and fatigue. The generated checklist adapts to the specific risk you are investigating, providing tailored checkpoint logs and a final PASS or FAIL verdict.