openclaw/docs/test.md

---
summary: "How to run tests locally (vitest) and when to use force/coverage modes"
read_when:
  - Running or fixing tests
---
# Tests

- `pnpm test:force`: Kills any lingering gateway process holding the default control port, then runs the full Vitest suite with an isolated gateway port so server tests don’t collide with a running instance. Use this when a prior gateway run left port 18789 occupied.
- `pnpm test:coverage`: Runs Vitest with V8 coverage. Global thresholds are 70% lines/branches/functions/statements. Coverage excludes integration-heavy entrypoints (CLI wiring, gateway/telegram bridges, webchat static server) to keep the target focused on unit-testable logic.
-												docs(site): refresh clawdis.ai for Pi

											
										
										
											2025-12-13 13:25:49 +00:00
+								---
 								summary: "How to run tests locally (vitest) and when to use force/coverage modes"
 								read_when:
 								  - Running or fixing tests
 								---
 								# Tests
-												test: add test:force helper

											
										
										
											2025-12-10 01:00:29 +00:00
-												chore(gateway): use ws bind as lock

											
										
										
											2025-12-11 15:17:40 +00:00
+								- `pnpm test:force`: Kills any lingering gateway process holding the default control port, then runs the full Vitest suite with an isolated gateway port so server tests don’t collide with a running instance. Use this when a prior gateway run left port 18789 occupied.
-												docs(site): refresh clawdis.ai for Pi

											
										
										
											2025-12-13 13:25:49 +00:00
+								- `pnpm test:coverage`: Runs Vitest with V8 coverage. Global thresholds are 70% lines/branches/functions/statements. Coverage excludes integration-heavy entrypoints (CLI wiring, gateway/telegram bridges, webchat static server) to keep the target focused on unit-testable logic.