soak-test

To create a soak test protocol, you specify a duration like 30m, 1h, 2h, or 4h. The tool then generates a markdown file with timed checkpoints, baseline setup, and post-session analysis sections to guide human testers through extended gameplay sessions.

Soak testing identifies issues that only appear after extended play, such as memory leaks, performance drift, state accumulation bugs, and player fatigue. You need it for pre-release polish, regression soaks after stability fixes, or formal QA endurance validation.

Yes, the soak test protocol includes engine-specific monitoring instructions for Godot, Unity, and Unreal. This ensures testers capture memory usage, object counts, and engine metrics correctly at each timed checkpoint during the playtest.

You structure QA endurance validation by generating a human-led protocol with pre-session setup, baseline metrics, checkpoint logs, and a final verdict. It supports both solo and co-op session-driven game loops to assess long-run stability and fun fatigue.

The best way to document memory leak observations is using the generated markdown protocol file. It provides a consistent set of timed checkpoints and observation fields, allowing testers to accurately record memory metrics and state accumulation for post-session analysis.