openclaw-qa-testing

Run qa-lab and qa-channel scenarios and generate artifacts and reports.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zhcndoc/openclaw --skill openclaw-qa-testing-zhcndoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-qa-testing
Source: https://github.com/zhcndoc/openclaw/tree/main/.agents/skills/openclaw-qa-testing
Command: npx skills add https://github.com/zhcndoc/openclaw --skill openclaw-qa-testing-zhcndoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and orchestrates repo-local QA workflows for qa-lab and qa-channel scenarios, artifacts, and live lanes, reducing manual setup and debugging.

Core Features & Use Cases

  • Repo-local QA orchestration for qa-lab and qa-channel scenarios
  • Read scenario packs, run live and mock lanes, and generate artifacts and reports
  • Explain and debug QA flows within a local OpenClaw workspace

Quick Start

Run the QA workflow in this repository using the standard pnpm commands to execute the live-lane QA suite

Frequently Asked Questions about openclaw-qa-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate repo-local QA scenario testing for OpenClaw?

Automating OpenClaw QA testing involves running standard pnpm commands in your repository to execute the live-lane suite, which reads scenario packs and orchestrates qa-lab and qa-channel workflows to generate artifacts and reports.

What are qa-lab and qa-channel scenario packs in OpenClaw testing?

OpenClaw scenario packs are configuration sets read by the QA tooling to define and execute specific testing workflows, coordinating either live-frontier or mock-openai models within a local OpenClaw workspace.

Do I need a local OpenClaw workspace to run QA workflows?

Yes, a local OpenClaw workspace with QA tooling installed is required to run these workflows, as the process reads scenario packs, coordinates models, and outputs results under the .artifacts/qa-e2e directory.

How does OpenClaw QA testing coordinate live-frontier and mock-openai models?

OpenClaw QA testing coordinates live-frontier or mock-openai models during scenario execution to validate workflows, automatically routing test outputs and debugging information into generated artifacts and logs.

Where are OpenClaw QA artifacts and debugging logs stored?

OpenClaw QA artifacts and debugging logs are stored under the .artifacts/qa-e2e directory in your repository, providing structured reports and output data for analyzing the executed scenario workflows.