zzos/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-09-28 22:15:22 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
openclaw/docs/help/testing.md
T
Vincent Koc 47ff7bfb11 docs: close remaining cross-link gaps across concepts, gateway, and security (#143923) 
Adds the missing reciprocal links and one mis-targeted link fix for the
last open `link` audit findings.

- Related back-links: system prompt (context engine, timezone), diagnostics
  flags (gateway diagnostics, gateway troubleshooting), cloud workers
  (operator scopes), auth credential semantics (secrets, auth storage),
  agent runtime architecture (agent runtimes), agent runtime workflow
  (testing), network (remote access, architecture), threat model (gateway
  security index, network proxy), backups/updating/doctor (database schemas).
- docs/security/network-proxy.md gains a Related section.
- docs/security/incident-response.md links back to the three sibling pages
  that already link to it.
- docs/concepts/typing-indicators.md links the heartbeat and groups pages
  that its Defaults section describes.
- docs/diagnostics/flags.md links the environment-variable reference from
  the timeline section that names three OPENCLAW_DIAGNOSTICS_* variables.
- docs/concepts/main-session.md names `session.maintenance.maxDiskBytes` and
  links the maintenance reference instead of stating a bare 10 GB default.
- docs/network.md pointed its "Gateway config reference" entry at
  /gateway/configuration; retargeted to /gateway/configuration-reference.
- docs/openclaw-agent-runtime.md merges its References list into Related and
  keeps the old `#references` anchor as a stub.
- Six zh-CN glossary sources added beside their related existing terms.
2026-09-10 18:34:34 +08:00

7.1 KiB
Raw Permalink Blame History

summary, read_when, title
summary read_when title
Index of the OpenClaw testing kit, one page per reader job
Running tests locally or in CI
Adding regressions for model/provider bugs
Debugging gateway + agent behavior
Testing

OpenClaw has three Vitest suites (unit/integration, e2e, live) plus Docker runners. This page covers what each suite covers, which command to run for a given workflow, how live tests discover credentials, and how to add regressions for real-world provider/model bugs.

**QA stack (qa-lab, qa-channel, live transport lanes)** is documented separately:
  • QA overview - architecture, command surface, scenario authoring, and the Matrix live lane.
  • Maturity scorecard - how release QA evidence supports stability and LTS decisions.
  • QA channel - the synthetic transport plugin used by repo-backed scenarios.

This page covers the regular test suites and Docker/Parallels runners. QA-specific runners below lists the concrete qa invocations and points back at the references above.

This page is an index. The testing kit is documented on six pages, one per reader job. Open the page that matches your task.

Page Read it when
Test suites and commands You need to pick a suite, a command, or the offline regression checks.
Live and Docker/Parallels workflows You are debugging a real provider or model through a live Docker or Parallels lane.
Docker test runners You want the Docker "works in Linux" lanes, their scheduler, and their env vars.
QA-specific runners You are running a QA Lab lane or need the shared Convex credential contract.
Contract tests You changed a channel, provider, or plugin-sdk surface.
Writing and adding tests You are writing a test, a regression, or a reliability eval.

Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /help/testing#qa-specific-runners still resolves. Each entry points at the page that now holds the content.

Related

Reference in New Issue View Git Blame Copy Permalink