Problem
pause_after is detected by key presence rather than truthiness:
https://github.com/http-tests/cache-tests/blob/main/test-engine/client/test.mjs#L54
pauseAfter: 'pause_after' in requests[i]
A request with pause_after: false would still pause, because the key is present.
Impact
Latent. The shared templates (tests/lib/templates.mjs) only ever set pause_after: true, and no test overrides it to false. But the field's false value is currently a no-op trap: anyone who writes pause_after: false (e.g. to override a template that sets it true) would not get the behavior they asked for.
Suggested fix
pauseAfter: requests[i].pause_after === true
Filed from an AI-assisted (Claude Code) review of the test harness, reviewed by a human before filing.
Problem
pause_afteris detected by key presence rather than truthiness:https://github.com/http-tests/cache-tests/blob/main/test-engine/client/test.mjs#L54
A request with
pause_after: falsewould still pause, because the key is present.Impact
Latent. The shared templates (
tests/lib/templates.mjs) only ever setpause_after: true, and no test overrides it tofalse. But the field'sfalsevalue is currently a no-op trap: anyone who writespause_after: false(e.g. to override a template that sets it true) would not get the behavior they asked for.Suggested fix
Filed from an AI-assisted (Claude Code) review of the test harness, reviewed by a human before filing.