qa

Coordinates automated Playwright and manual QA routes with evidence capture for bug reports.

2|Updated Oct 2, 2025

Search Tags:#automation #qa #playwright #bug-reporting #volume #exploratory-testing #evidence-capture

Ready to run

npx skills add https://github.com/misty-step/volume --skill qa-misty-step

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/qa
Command: npx skills add https://github.com/misty-step/volume --skill qa-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Browser-based QA, exploratory testing, evidence capture, and bug reporting help teams verify software behavior beyond pass/fail test results.

Core Features & Use Cases

Automated Playwright-based end-to-end tests alongside a tailored manual QA companion workflow.
Evidence generation including screenshots, GIFs, videos, and logs for bug reports.
Route-coordinated QA scenarios to validate auth, payments, and feature flows in volume.fitness.

Quick Start

Run the QA workflow on your Volume app and capture evidence using the provided tooling.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I capture evidence for bug reports during exploratory testing?▼

Evidence capture for bug reports involves generating screenshots, GIFs, videos, and logs during exploratory testing to document issues. This Skill orchestrates browser-based QA workflows to automatically produce these artifacts for reliable software behavior validation.

What do I need to run browser-based QA and reproduce issues safely?▼

To reproduce issues safely during browser-based QA, you need a browser automation tool, access to a running dev server, and documented test credentials or fixtures. These prerequisites ensure reliable evidence capture and consistent test execution.

How does route-coordinated QA validate auth and payment flows in volume.fitness?▼

Route-coordinated QA validates auth and payment flows in volume.fitness by applying automated Playwright tests and manual QA routes to specific feature paths. This end-to-end validation captures evidence artifacts to ensure reliable software behavior across critical user journeys.

Are there limitations when using automated tests instead of exploratory testing?▼

Automated tests validate predefined paths but may miss unexpected defects found through exploratory testing. This Skill combines automated Playwright end-to-end tests with a manual QA companion workflow, sharing evidence artifacts like screenshots and logs to bridge the gap between pass/fail results and comprehensive bug reporting.