mirror of
https://github.com/hansjone/oclaw.git
synced 2026-10-14 06:43:16 +08:00
oliver
dbbe3add6a
同时收敛启动与运维脚本默认行为（含 wiki worker）、更新 Admin 可观测性与相关测试，降低首轮时延并提高运行稳定性。 Made-with: Cursor
77 lines
3 KiB
Markdown
77 lines
3 KiB
Markdown
# OpenClaw QA Scenario Pack
|
|
|
|
Single source of truth for repo-backed QA suite bootstrap data.
|
|
`qa-lab` should treat this directory as a generic markdown scenario pack:
|
|
|
|
- `index.md` defines pack-level bootstrap data
|
|
- each nested `*.md` scenario defines one runnable test via `qa-scenario` + `qa-flow`
|
|
- scenario markdown may also define coverage IDs, category metadata, required plugins,
|
|
lane filters, and gateway config patching
|
|
|
|
- kickoff mission
|
|
- QA operator identity
|
|
- scenario files under one-level theme directories
|
|
|
|
Coverage tracking:
|
|
|
|
- add `coverage.primary` IDs to each scenario's `qa-scenario` block
|
|
- add `coverage.secondary` only when a scenario intentionally protects another behavior
|
|
- keep IDs behavior-shaped, broad enough to reuse, lowercase, and dotted or dashed
|
|
- prefer reusing an existing feature ID over minting a scenario-shaped ID
|
|
- avoid copying the scenario title into coverage IDs
|
|
- use `pnpm openclaw qa coverage` to render the current inventory
|
|
- treat the old `coverage: ["id"]` / `coverage: - id` list shape as invalid
|
|
- keep source-path tracking in the report, not in the scenario schema
|
|
|
|
Theme directories:
|
|
|
|
- `agents/` - agent behavior, instructions, and subagent flows
|
|
- `channels/` - DM, shared channel, thread, and message-action behavior
|
|
- `character/` - persona and style eval scenarios
|
|
- `config/` - config patch, apply, and restart behavior
|
|
- `media/` - image understanding and generation
|
|
- `memory/` - recall, ranking, active memory, and thread isolation
|
|
- `models/` - provider capabilities and model switching
|
|
- `plugins/` - plugin, skill, and MCP tool integration
|
|
- `runtime/` - turn recovery, compaction, approval, and inventory behavior
|
|
- `scheduling/` - cron and recurring work
|
|
- `ui/` - Control UI plus qa-channel flows
|
|
- `workspace/` - repo-reading and workspace artifact tasks
|
|
|
|
```yaml qa-pack
|
|
version: 1
|
|
agent:
|
|
identityMarkdown: |-
|
|
# Dev C-3PO
|
|
|
|
You are the OpenClaw QA operator agent.
|
|
|
|
Persona:
|
|
- protocol-minded
|
|
- precise
|
|
- a little flustered
|
|
- conscientious
|
|
- eager to report what worked, failed, or remains blocked
|
|
|
|
Style:
|
|
- read source and docs first
|
|
- test systematically
|
|
- record evidence
|
|
- end with a concise protocol report
|
|
kickoffTask: |-
|
|
QA mission:
|
|
Understand this OpenClaw repo from source + docs before acting.
|
|
The repo is available in your workspace at `./repo/`.
|
|
Use the seeded QA scenario plan as your baseline, then add more scenarios if the code/docs suggest them.
|
|
Run the scenarios through the real qa-channel surfaces where possible.
|
|
Track what worked, what failed, what was blocked, and what evidence you observed.
|
|
End with a concise report grouped into worked / failed / blocked / follow-up.
|
|
|
|
Important expectations:
|
|
|
|
- Check both DM and channel behavior.
|
|
- Include a Lobster Invaders build task.
|
|
- Include a cron reminder about one minute in the future.
|
|
- Read docs and source before proposing extra QA scenarios.
|
|
- Keep your tone in the configured dev C-3PO personality.
|
|
```
|