openclaw-test-performance skill

OpenClaw Test Performance

Use evidence first. The goal is real pnpm test, plugin-suite, and plugin-inspector speed/RSS improvement with coverage intact, not runner tuning by guesswork.

Workflow

1. Read the relevant local AGENTS.md files before editing:

laziness.

• src/agents/AGENTS.md for agent/import hotspots.
• src/channels/AGENTS.md and src/plugins/AGENTS.md for plugin/channel

src/channels/plugins/contracts/test-helpers/AGENTS.md for shared contract helpers.

• src/gateway/AGENTS.md for server lifecycle tests.
• test/helpers/AGENTS.md and

• src/infra/outbound/AGENTS.md for outbound/media/action tests.

1. Establish a baseline before changing code:

for full-suite ranking.

• Prefer pnpm test:perf:groups --full-suite --allow-failures --output

test:extensions:batch or plugin-inspector command before jumping to the full extension sweep.

• For bundled plugin breadth, run the smallest relevant pnpm

/usr/bin/time -l pnpm test --maxWorkers=1 --reporter=verbose

• For a scoped hotspot use:

OPENCLAWVITESTIMPORTDURATIONS=1 OPENCLAWVITESTPRINTIMPORT_BREAKDOWN=1.

• For import-heavy suspicion add:

1. Separate wall/runner noise from real file cost:

max RSS.

• Compare Vitest duration, test body timing, import breakdown, wall time, and

passed, capture that as harness/noise and verify the suspect file directly.

• Re-run single files when grouped/full-suite numbers look stale or noisy.
• If a full-suite grouped run reports a lane failure but JSON says tests

1. Pick the next attack by return and risk:

extension-batch run to load broad runtime.

• High return: one file/test dominates seconds or RSS and has a clear root.
• High leverage: one plugin or SDK barrel causes every plugin-inspector or

setup hints, registry fixtures, or test server lifecycle.

• Lower risk: static descriptors, target parsing, routing, auth bypass,

contracts, or broad production refactors.

• Higher risk: real memory/runtime behavior, live providers, protocol

1. Fix the root cause, not the symptom:

reused by full runtime and fast paths.

• Move static metadata/parsing into narrow helpers or lightweight artifacts

and pure helpers over broad mocks.

• Prefer dependency injection, loaded-plugin-only lookup, explicit fixtures,

and keep runtime plugin loads behind explicit execution boundaries.

• Reuse suite-level servers/clients when a fresh handshake is irrelevant.
• Keep schedulers/background loops off unless the test proves scheduling.
• In plugin paths, move static metadata into manifest/lightweight artifacts

1. Preserve coverage shape:

composition is extracted into a named helper and tested.

• Do not delete a slow integration proof unless the exact production

• Keep one cheap integration smoke when cross-component wiring matters.
• State explicitly what incidental coverage was removed, if any.

percent gain.

1. Re-benchmark the same command after the change and compute seconds plus

Include before/after commands, artifacts, coverage notes, verification, and next attack order.

1. Update the running report when requested or when this thread is tracking one.

user asked for commits/pushes. Stage only files touched for this attack.

1. Stage the intended paths, commit with standard Git, and push when the

Plugin-Suite Workflow

Use this section when perf work involves bundled plugins, plugin-inspector, SDK barrels, package-boundary tests, or extension suites.

1. Map the suite shape first:

pnpm run test:extensions:package-boundary:compile

• source tests: pnpm test extensions/ or pnpm test:extensions:batch
• package boundaries: pnpm run test:extensions:package-boundary:canary and

keep wrappers thin and collect peak RSS when the command supports it.

• all bundled source tests: pnpm test:extensions
• plugin import memory: pnpm test:extensions:memory -- --json .artifacts/test-perf/extensions-memory.json
• plugin-inspector/report work: keep report primitives in plugin-inspector;

1. Start narrow, then widen:

and feature plugins.

• one plugin changed: run that plugin's tests and plugin-inspector slice.
• SDK/public barrel changed: add representative provider, channel, memory,

proof as needed.

• loader/runtime mirror changed: add package-boundary checks and build/package

pnpm test:extensions.