Imported from openclaw-easy/openclaw-easy-desktop (
openclaw/src/agents/embedded-agent-runner/run/AGENTS.md). Install upstream withnpx skills add openclaw-easy/openclaw-easy-desktop --skill run. Copyright stays with the author.
Embedded Runner Test Performance
The embedded attempt runner is one of the most expensive agent test surfaces. Use full-runner tests only when the behavior truly requires the runner.
Guardrails
- Prefer focused helper tests for prompt assembly, runtime-context construction, cache metadata, token accounting, and maintenance decision logic.
- Keep full
runEmbeddedAttemptcoverage for cross-component behavior that cannot be proven through helpers, not for a single derived field. - When extracting a helper from runner logic, make production call that helper directly, then test the helper. Avoid test-only copies of runner behavior.
- Preserve context-engine coverage for
sessionKey,sessionFile, token budget, current token count, prompt cache, and routing fields when slimming tests. - Treat a standalone full-runner test above a few seconds as suspect. First ask whether the proof can move to a production helper plus one cheap integration smoke.
Verification
- For runner test slimming, run the touched helper test and the nearest two-file runner/context-engine surface.
- Record Vitest duration, wall time, and RSS when the change is performance motivated.