qa

Automate end-to-end web application testing with bug detection and evidence capture.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA workflow automates end-to-end testing of a web application, surfacing regressive bugs and ensuring fixes are verified before release.

Core Features & Use Cases

  • End-to-end QA workflow with bug identification and evidence capture
  • Iterative fixes in source code with atomic commits and re-verification
  • Tiered testing: Quick, Standard, Exhaustive, plus ship-readiness summaries
  • Proactive suggestions when features are ready for testing

Quick Start

Provide the target URL and scope, and I will start the QA cycle.

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 regression testing for a web application?▼

Automated end-to-end regression testing runs a defined set of deterministic test scenarios against your web app to surface bugs and verify fixes before release. It captures evidence using before and after health scores to ensure ship-readiness.

What is a ship-readiness summary in a QA workflow?▼

A ship-readiness summary is the final output of a QA workflow cycle that verifies source code fixes through atomic commits. It confirms that previously identified regressive bugs are resolved and provides health scores to validate release confidence.

How do I verify bug fixes without disrupting my existing web testing environment?▼

You can verify bug fixes by applying iterative changes to your source code using atomic commits. The QA workflow then automatically re-verifies the application under test against the defined scenarios to ensure the fix is successful before moving forward.

Do I need a dedicated test environment to run automated regression tests?▼

Yes, automated regression testing requires a working test environment, access to the application under test, and a defined set of test scenarios. These elements must run deterministically to accurately capture before and after health scores.

Can I run different levels of regression testing for daily and weekly release cycles?▼

Yes, the QA workflow supports tiered testing including Quick, Standard, and Exhaustive levels. This allows you to scale end-to-end testing appropriately across daily, weekly, and full release cycles to match your specific verification needs.