qa

Automate end-to-end QA testing of web applications with three scoped tiers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

Core Features & Use Cases

  • Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying.
  • Produces before/after health scores, fix evidence, and a ship-readiness summary.
  • Proactively suggest QA findings when relevant or requested, and support a /qa-only report mode.
  • Supports three tiers (Quick, Standard, Exhaustive) to control scope and depth.

Quick Start

Run a complete QA pass on the active web app and report issues with evidence.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate end-to-end QA testing and fix bugs in my web application?

Automated end-to-end QA testing runs test passes on your web application, logs discovered defects, iteratively fixes bugs in source code with atomic commits, and re-verifies the fixes. It captures before and after health scores to confirm ship-readiness.

What is the best way to scope automated web app testing to focus only on critical bugs?

To scope automated web app testing for critical bugs, use the Quick tier, which targets only critical and high-priority defects. Standard adds medium severity, while Exhaustive includes cosmetic issues, allowing you to control testing depth and resource usage.

Can I generate a QA report without automatically modifying my source code?

Yes, you can generate a QA report without modifying source code by using the report-only mode. This mode executes the testing pass and logs defects with evidence but skips the iterative bug-fixing and atomic commit workflow.

How does automated bug fixing verify that a source code fix actually resolves the defect?

Automated bug fixing verifies each resolution by iteratively applying a source code fix, committing it atomically, and then re-running the QA test to confirm the defect is closed. It tracks before and after health scores to provide fix evidence.

What does a ship-readiness summary include after a QA testing pass?

A ship-readiness summary includes the web application's before and after health scores, evidence of applied bug fixes, and a status report on remaining defects. It confirms whether the application meets the criteria for deployment based on the selected tier.