qa

Name: qa
Availability: InStock
Author: Yaugourt

Identify and fix web application bugs through structured test runs and atomic commits.

2|2|Updated Dec 1, 2024

Search Tags:#automation #testing #qa #verification #atomic-commits #bug-fix #web-app

Ready to run

npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill qa-yaugourt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack/qa
Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill qa-yaugourt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the QA process by guiding testers to systematically explore a web application, reproduce bugs, and fix them with atomic commits.

Core Features & Use Cases

Systematic testing by acting like a real user: clicking, form filling, and state checks.
End-to-end bug fixing: reproduce, fix in source, commit atomically, and re-run tests.
Reporting and health feedback: before/after tests, evidence, and ship-readiness summaries.

Quick Start

Run the QA workflow on the current branch to test, fix, commit atomically, and 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 end-to-end QA and bug fixing for a web application?▼

Automate end-to-end QA by running structured tests that act like a real user, reproducing bugs, fixing them in source code, and committing each fix atomically. The workflow re-runs tests to verify fixes and generates a final health report.

What is the best way to structure commits when fixing regression bugs in web apps?▼

The best way to structure commits for regression bugs is using atomic commits. This means each isolated bug fix is committed individually after re-running tests to verify the fix, ensuring a clean working tree and traceable changes.

Do I need a clean working tree to run automated QA tests on new code changes?▼

Yes, you need a clean working tree before starting automated QA tests. The process requires access to the project and the ability to create atomic commits for each fix, which prevents conflicts and ensures accurate regression verification.

How does automated QA reporting work for web app user flows?▼

Automated QA reporting works by comparing before and after test runs across multiple pages and user flows. It collects evidence and generates a ship-readiness summary to indicate the health of the application after fixes.

Can I use automated testing to reproduce and fix bugs across multiple pages simultaneously?▼

Yes, you can use automated testing to reproduce and fix bugs across multiple pages and user flows. The systematic testing process simulates real user interactions like clicking and form filling, then applies atomic commits for each resolved issue.