openclaw/qa
Peter Steinberger 0ec41639b1
fix(reply): report failures after a turn is accepted (#133979)
* fix(reply): report failures after a turn is accepted

* test(codex): prepare runtime policy in credential wait fixture
2026-08-31 02:57:26 -07:00
..
convex-credential-broker feat(qa): add Convex-leased Telegram userbot proof (#131715) 2026-08-29 07:56:30 +05:30
scenarios fix(reply): report failures after a turn is accepted (#133979) 2026-08-31 02:57:26 -07:00
frontier-harness-plan.md
maturity-scores.yaml refactor(canvas): make the panel a widget presenter (#126030) 2026-08-19 08:21:07 -07:00
README.md
scenarios.md

QA Scenarios

Seed QA assets for the private qa-lab extension.

Files:

  • scenarios/index.yaml - canonical QA scenario pack, kickoff mission, and operator identity.
  • scenarios/<theme>/*.yaml - one runnable scenario per YAML file.
  • frontier-harness-plan.md - big-model bakeoff and tuning loop for harness work.
  • convex-credential-broker/ - standalone Convex v1 lease broker for pooled live credentials.

Key workflow:

  • qa suite is the executable frontier subset / regression loop.
  • qa manual is the scoped personality and style probe after the executable subset is green.
  • qa coverage prints the scenario coverage inventory from scenario YAML.

Operator workflows:

  • Use the openclaw-qa-testing skill for QA Lab live lanes, Convex credential pool operations, and WhatsApp live credential setup/replacement.

Keep this folder in git. Add new scenarios here before wiring them into automation.