soak test
Running a device for days under realistic load while logging what drifts, such as free memory.
A soak test runs a device continuously for an extended period, often with faults injected on a schedule, logging slowly drifting quantities (free heap, largest free block, reset reasons, retry counts) to expose leaks, fragmentation and overflows.
Examples
A 72 h soak restarts the broker every 2 h and passes only if free heap stays flat and the reconnect count equals the restart count.
A leak of a few bytes per reconnect only shows when the soak runs longer than free heap divided by bytes lost per hour.
See also