About this skill

Problem

Test case design often stalls before method selection: requirements are scattered across chat messages, screenshots, and document fragments, while field boundaries, permission differences, and state transitions are easy to miss. This skill focuses on functional testing by turning informal requirement input into traceable design inputs and an executable case sheet.

How It Works

Requirement extraction: collects function points, input domains, constraints, boundary values, business flows, state transitions, and roles from text, docx, pdf, or screenshots, marking items as user-stated or inferred.
Confirmation and calibration: requires user confirmation before case design and corrects obvious common-sense errors, such as mobile number length, ID card type, or negative amounts.
Case design: selects at least three techniques, such as scenario-based, equivalence partitioning, boundary analysis, decision tables, or state transition, then deduplicates and orders cases as normal, boundary, exception, and combination.
Output generation: produces a blue-themed Word requirement document and a blue-header Excel case sheet with TC-001 IDs, preconditions, steps, expected results, and notes.

Boundaries

Best for well-scoped functional tests such as login, forms, payments, permissions, or state machines. Performance and compatibility testing are added only on explicit request. Severe requirement gaps trigger follow-up questions; after two rounds, design continues from known information and assumptions are labeled.

Screenshots

Use Cases

Turn a login requirement with phone number, password length, and lockout rules into boundary, state-transition, and Excel test cases.
From PRD fragments and field tables, extract input domains, constraints, and flows, then generate a Word summary plus equivalence and boundary cases.
For form rules with required fields, length limits, exclusions, and permission differences, produce grouped normal, boundary, exception, and combination cases.
When compatibility testing is requested, add Chrome, Firefox, Edge, and resolution targets to case notes.

Best For

Functional testers owning login, payment, or permission modules who need to turn verbal requirements into executable case sheets.
Test leads taking over an old PRD who need to complete input domains, state transitions, and boundary coverage.
Case-design owners who must deliver requirement summaries with source labels in Word and Excel.
Product managers validating frontend-backend integration scenarios who need exception flows and role permissions covered.