What problem does it solve?
It helps teams translate product changes and design intent into clear, structured QA outputs (test plans, test cases, regression suites, Figma validation checks, and bug reports) so QA engineers can execute consistently and efficiently.
Core Features & Use Cases
- Test plans: Produces a full test plan with objectives, scope, test strategy, automation strategy, environment requirements, entry/exit criteria, risk assessment, and timeline.
- Test cases: Generates functional, UI/visual, integration, regression, security, performance, and smoke test cases with IDs and explicit automation annotations.
- Regression suites: Builds regression suite documents with tiers (Smoke/Targeted/Full/Sanity), prioritization rules, execution order, and pass/fail criteria.
- Figma validation support: Creates UI/visual test cases (TC-UI-*) and guides discrepancies into structured bug reports when Figma MCP is configured.
- Bug reports: Generates bug reports (BUG-*) in the unified template, including severity, priority, environment, reproduction, expected vs actual, and automation follow-up guidance.
Quick Start
Generate a test plan and test cases for your feature by asking: "Create test plan and test cases for the new checkout flow, store everything under ./artifacts, and include UI checks against the provided Figma designs."