qa-test-design

Extract QA perspectives from specs, code, PRs, UI, and APIs for test design.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/takuto277/levelup-study --skill qa-test-design-takuto277
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-test-design
Source: https://github.com/takuto277/levelup-study/tree/main/.cursor/skills/qa-test-design
Command: npx skills add https://github.com/takuto277/levelup-study --skill qa-test-design-takuto277

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA teams and developers often struggle to systematically extract QA perspectives from specifications, code, PRs, UI, and APIs before writing tests, leading to incomplete test coverage and missed failure modes.

Core Features & Use Cases

  • Systematic viewpoint extraction to generate comprehensive test cases covering equivalence partitions, boundary conditions, decision tables, and state transitions.
  • Risk-aware review workflow with a checklist-driven test case catalog ready for implementation.
  • Guidance on resolving ambiguities and documenting test-coverage gaps to improve communication between product, design, and engineering.

Quick Start

Describe the target artifact (API, UI, or feature) and ask for a complete QA perspective and test-case outline.

Frequently Asked Questions about qa-test-design

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

FAQPage Schema
How do I systematically extract QA test perspectives from API and UI specifications?

Test design uses equivalence partitioning, boundary analysis, decision tables, and state transitions to extract QA perspectives from API and UI specifications, yielding a checklist-driven test case catalog covering common and edge cases.

What is the best way to design test cases using equivalence partitioning and boundary analysis?

Equivalence partitioning and boundary analysis drive test design by systematically dividing input domains into valid and invalid classes, then testing boundary values to generate comprehensive test cases that expose edge-case failures.

How do I create a decision table for state transition test design?

Decision tables and state transitions map complex business rules and system states into structured matrices, enabling systematic test case generation that validates all valid paths, invalid transitions, and risk patterns.

Can I generate a checklist-driven test case catalog from source code and pull requests?

Yes, this approach extracts QA perspectives directly from source code, pull requests, UI, and APIs to generate a risk-aware, checklist-driven test case catalog ready for implementation across integration scenarios.

Does this test design method help resolve specification ambiguities and document coverage gaps?

Risk-based checks and systematic viewpoint extraction identify specification ambiguities and document test-coverage gaps, improving communication between product, design, and engineering teams before implementation.

When should I use risk-based testing over standard test case generation?

Risk-based testing prioritizes failure modes and edge cases when specifications are ambiguous or integration scenarios are complex, ensuring checklist-driven coverage targets the highest risk patterns first.