qa-only

Automate browser-based QA tests and generate evidence reports.

Updated Mar 16, 2026

Search Tags:#reports #screenshots #qa #evidence #playwright #browser-automation

Ready to run

npx skills add https://github.com/dmulcahey/featureforge --skill qa-only-dmulcahey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/dmulcahey/featureforge/tree/main/skills/qa-only
Command: npx skills add https://github.com/dmulcahey/featureforge --skill qa-only-dmulcahey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA-Only provides browser-based quality assurance tooling that captures repro steps, evidence, and reports without requiring code changes to your application.

Core Features & Use Cases

Automated browser-based QA across pages and flows
Evidence capture including screenshots, console logs, and network traces
Generated QA reports for audit and sharing with stakeholders
Non-invasive testing workflow suitable for quick smoke checks and full regression
Optional support for test plans and matrices to guide coverage

Quick Start

Run qa-only against your web application to automatically collect screenshots, logs, and a comprehensive QA report without modifying the app code.

Frequently Asked Questions about qa-only

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

FAQPage Schema

How do I automate browser QA to collect screenshots and console logs without changing my application code?▼

Automated browser QA collects screenshots, console logs, and network traces as evidence without altering your application code. It safely runs smoke checks and full regression tests across multiple pages, viewports, and user flows to generate comprehensive reports.

Can I run automated regression tests across multiple viewports and user flows non-invasively?▼

Automated regression tests run non-invasively across multiple viewports and user flows without modifying your web application. The workflow safely guides coverage using optional test plans and matrices while capturing evidence for audit and stakeholder sharing.

What is the best way to generate QA reports with network traces and evidence for stakeholders?▼

Generating QA reports with network traces involves capturing browser evidence during automated web application testing. This process automatically compiles screenshots, logs, and traces into comprehensive reports suitable for audit and sharing without requiring code changes.

Does browser automation testing work for both quick smoke checks and full regression QA?▼

Browser automation testing works for both quick smoke checks and full regression QA. It applies a non-invasive workflow to capture repro steps and evidence across pages, generating reports without altering the underlying application code.

How do I capture network traces and console logs during web application testing?▼

Capturing network traces and console logs during web application testing is automated through browser-based QA tooling. This evidence collection process runs safely without code changes, supporting quick checks and full regression matrices for stakeholder reports.

Why do I need to use test plans and matrices when automating browser-based QA?▼

Test plans and matrices guide coverage when automating browser-based QA, ensuring evidence capture spans multiple pages, viewports, and user flows. This structured approach guarantees comprehensive reports without altering your web application code.