qa-only

Run report-only QA tests on a web application and generate a health score, screenshots, and reproducible steps.

Updated Dec 22, 2019
One-click install
npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill qa-only-sajalsuhane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/sajalsuhane/sajalsuhane.github.io/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill qa-only-sajalsuhane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing isolates the QA activity to observation and documentation, generating structured reports without applying any fixes, so teams can triage issues accurately.

Core Features & Use Cases

  • Systematic, report-only tests that document bugs and issues without modifying the codebase.
  • Generates a health score, screenshots, and reproducible steps for each finding to aid triage and communication.
  • Use cases include responding to requests like "just report bugs" or "qa report only"; for a full test-fix-verify loop, use /qa.

Quick Start

Run the QA workflow against the current target URL to generate a report without applying any fixes.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate a QA report for a web application without modifying the codebase?

Report-only QA testing generates a structured health score, screenshots, and reproducible steps without modifying the codebase. It systematically tests the target URL to document bugs and issues so teams can triage findings accurately.

What is included in an automated report-only QA test result?

Report-only QA test results include a structured health score, screenshots, and reproducible steps for each finding. These outputs document bugs and issues to aid triage and team communication.

When should I use a report-only QA workflow instead of a full test-fix-verify loop?

Use report-only QA when you need to isolate observation and documentation without code changes. Use a full test-fix-verify loop when you want the workflow to apply fixes and verify the changes.

Can I capture screenshots and reproducible steps for bugs without touching the source code?

Yes, report-only QA testing captures screenshots and reproducible steps without touching the source code. The workflow documents issues strictly for triage and proactively suggests when a bug report is useful.

What are the limitations of a report-only QA testing approach?

Report-only QA testing is limited to observation and documentation, meaning it will not apply any code fixes. If you need automated remediation, use a full test-fix-verify loop instead of the report-only workflow.