qa

Test web applications by simulating user interactions and generate QA reports.

9|3|Updated Jan 29, 2022
One-click install
npx skills add https://github.com/I194/PMTools_2.0 --skill qa-i194
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/I194/PMTools_2.0 --skill qa-i194

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically QA test web applications like a real user, identify bugs, and drive fixes with atomic commits.

Core Features & Use Cases

  • Test web applications by simulating real user interactions: click controls, fill forms, and verify states across pages.
  • Produce structured QA reports with before/after evidence, health scores, and ship-readiness assessments.
  • Integrate iterative fixes directly into the source with atomic commits and re-verify to close loop quickly.

Quick Start

Open the target URL, run through representative test flows, and fix bugs in source code with atomic commits, then re-verify.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web application QA testing by simulating real user interactions?

Web application QA testing automates real user interactions by clicking controls, filling forms, and validating every state across pages to identify bugs systematically. It simulates representative user flows to ensure application states behave correctly before shipping.

How does bug fixing with atomic commits work during QA testing?

Bug fixing with atomic commits integrates iterative fixes directly into the source code during QA testing. Each fix is committed atomically and then re-verified by testing the web application to close the loop quickly and ensure the issue is resolved.

What is a structured QA report with health scores and ship-readiness insights?

A structured QA report provides before and after evidence of bug fixes, calculates health scores, and delivers ship-readiness insights. It assesses the overall quality of the web application to determine if it is ready for release.

How to manually test web applications and generate ship-readiness assessments?

To manually test web applications, open the target URL and run through representative test flows by simulating user clicks and form inputs. The process generates ship-readiness assessments by validating states and fixing bugs with atomic commits before re-verification.

Can I fix source code bugs and re-verify them automatically during manual testing?

Yes, you can fix source code bugs and re-verify them during manual testing by implementing iterative fixes directly in the source with atomic commits. The skill automatically re-tests the application to confirm the bug is resolved.

What is the best way to track bug fixes with before and after evidence?

Tracking bug fixes with before and after evidence is best handled by generating structured QA reports during the testing process. These reports capture the state before the fix and the state after re-verification to provide clear proof of resolution.