acceptance-test-runner

Run acceptance tests and generate evidence-backed validation reports for PRD requirements.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bjornslib/cobuilder-harness --skill acceptance-test-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance-test-runner
Source: https://github.com/bjornslib/cobuilder-harness/tree/main/.claude/skills/acceptance-test-runner
Command: npx skills add https://github.com/bjornslib/cobuilder-harness --skill acceptance-test-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Acceptance test execution and evidence-based reporting are automated to verify PRD compliance and reduce manual QA effort.

Core Features & Use Cases

  • Automated end-to-end acceptance testing orchestration across browser and API validations
  • Evidence collection and generation of validation reports with structured results
  • Result aggregation and artifact storage under acceptance-tests/{PRD_ID}/runs for traceability

Quick Start

Invoke the acceptance-test-runner with a PRD identifier to run the full suite and generate the validation report.

Frequently Asked Questions about acceptance-test-runner

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

FAQPage Schema
How do I automate acceptance test execution and generate evidence reports for PRD validation?

You can automate acceptance test execution by invoking the runner with a PRD identifier to orchestrate browser or API tests, capture validation evidence, and generate a final markdown report. It stores all run artifacts under acceptance-tests/PRD-*/runs for traceability.

What is evidence-backed validation reporting for end-to-end acceptance tests?

Evidence-backed validation reporting is the process of executing acceptance criteria against a PRD and capturing concrete test artifacts. This runner collects outputs during browser or API test execution and aggregates them into a structured markdown summary to verify compliance.

How do I run acceptance tests across both browser and API validations?

To run acceptance tests across browser and API validations, invoke the runner with your target PRD identifier. It orchestrates test definitions across both environments, executes the validations, and aggregates the results into a single evidence-backed report.

Can I use this acceptance test runner for end-to-end validation without manual QA effort?

Yes, you can use this runner for end-to-end validation to reduce manual QA effort. It automates criterion execution and evidence collection across browser and API acceptance tests, producing a final markdown report to verify PRD requirements automatically.

Where are acceptance test run artifacts and evidence reports stored for traceability?

Acceptance test run artifacts and evidence reports are stored under the acceptance-tests/{PRD_ID}/runs directory. This structured storage ensures full traceability of validation results and collected evidence for each specific PRD requirement check.

What is the best way to verify PRD compliance using automated acceptance tests?

The best way to verify PRD compliance is automating acceptance test execution with a PRD identifier to run the full suite. This generates an evidence-backed validation report that aggregates structured results from browser and API tests into a final markdown summary.