Overview

QA Testing automates generation and execution of API and E2E tests, with a built‑in quality gate assessment. Quinn the QA Engineer drives tests for new endpoints, critical user flows, edge cases from code reviews, regression runs, and coverage reporting, delivering actionable results.

How This Skill Works

Inputs like projectName, storyResults, and optional codeReview feed the process. The agent generates API tests for new endpoints, creates E2E tests for critical user flows, tests edge cases from code review findings, runs regression tests, and then produces a coverage percentage, test results, and a quality gate status.

When to Use It

• When introducing new API endpoints to ensure both API and E2E coverage
• Before sprint releases to validate regression safety and quality gates
• When code review highlights edge cases that need testing
• During ongoing QA cycles to maintain regression coverage and metrics
• When you need a formal quality gate recommendation and test details

Quick Start

1. Step 1: Provide inputs: projectName, storyResults, and optional codeReview
2. Step 2: Run QA Testing to generate API tests and E2E tests for coverage
3. Step 3: Review test results, coverage percentage, and quality gate status

Best Practices

• Capture and incorporate code review findings to guide edge-case tests
• Always generate both API tests and E2E flows for critical user journeys
• Run regular regression tests and track coverage percentage
• Review test results and failed test details promptly
• Use quality gate status to inform release readiness and manual testing needs

Example Use Cases

• New user signup API paired with end-to-end signup flow tests
• Payment endpoint integration tests with end-to-end checkout flow
• User profile update API tested alongside a profile edit E2E path
• Edge-case scenarios like missing required fields and invalid data types
• End-to-end regression on order placement and fulfillment workflows

Frequently Asked Questions