qa-only

Run report-only QA tests on web apps and generate health scores, screenshots, and repro steps.

Updated Sep 10, 2024
One-click install
npx skills add https://github.com/TioSavich/UMEDCTA --skill qa-only-tiosavich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/TioSavich/UMEDCTA/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/TioSavich/UMEDCTA --skill qa-only-tiosavich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill performs report-only QA testing on a web application, generating a structured health score, annotated screenshots, and reproducible steps, while never applying fixes.

Core Features & Use Cases

  • Systematically tests a web app and produces a health score, screenshots, and repro steps.
  • Produces a detailed bug-report without modifying the codebase, suitable for "just report bugs" or "qa report only" workflows.
  • Works in both diff-aware mode (no URL on a feature branch) and full mode (URL provided), adapting test scope accordingly.

Quick Start

Invoke a full report-only QA run on the target site and generate a structured bug-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 run report-only QA tests on a web application without applying fixes?

You can run report-only QA tests by invoking the skill on your target web application to generate a structured health score, annotated screenshots, and reproducible steps without modifying the codebase.

Can I generate a bug report with annotated screenshots for my web app automatically?

Yes, automated browser testing captures annotated screenshots and generates a structured bug report containing a health score and reproducible steps for every detected issue in your web app.

How does diff-aware QA testing work when testing a feature branch without a URL?

Diff-aware QA testing adapts the test scope by analyzing changes on a feature branch when a URL is not provided, ensuring only the modified areas of the web application are evaluated for bugs.

What is the difference between diff-aware mode and full mode for web app QA reports?

Diff-aware mode scopes testing to feature branch changes without a URL, while full mode executes comprehensive QA testing across the entire web application when a direct URL is provided.

Do I need a browser automation tool to capture evidence for bug reports?

Yes, the skill relies on a browser automation tool to capture evidence for each issue, systematically executing web app tests and producing annotated screenshots for the final bug report.

Can I use optional resources like scripts and references during QA testing?

Yes, the skill reads optional resources from scripts, references, and assets as directed by its configuration, integrating custom test parameters into the report-only QA workflow.