qa

Run automated tests, collect failures, and apply atomic patches to web applications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing and bug fixing can be slow and error-prone. This skill orchestrates end-to-end QA by running tests, surfacing failures, and applying atomic fixes with automatic re-verification to guard against regressions.

Core Features & Use Cases

  • End-to-end QA orchestration: run tests, analyze failures, and commit small, reviewable fixes.
  • Health scoring and evidence: generate before/after health scores and attach evidence to guide ship decisions.
  • Ship-readiness summaries: produce concise summaries highlighting readiness after verification.

Quick Start

Run the QA workflow on your repository to test, fix, and verify changes end-to-end.

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 bug fixing for a web app?

End-to-end QA testing and bug fixing is automated by running tests, collecting failures, and applying atomic patches with automatic re-verification to guard against regressions across web app features and UI.

What is an atomic patch in automated QA workflows?

An atomic patch is a small, reviewable code fix applied after QA tests surface a failure. It is automatically re-verified by the testing workflow to ensure the bug fix succeeds without causing regressions.

Can I run automated tests without applying code fixes?

Yes, you can run automated tests without applying fixes by using the report-only mode. This option executes standard regression and exhaustive checks to generate failure reports and health scores without modifying the web application.

How do I generate a ship-readiness summary with health scores?

Ship-readiness summaries are generated after running exhaustive checks by calculating before and after health scores, attaching evidence of test results, and highlighting verification status to guide your deployment decisions.

Does this QA testing approach work for iterative web app development?

Yes, this QA testing approach is designed specifically for iterative development workflows on web apps, enabling quick triage of failures, standard regression checks, and exhaustive verification across features and UI before shipping.