Test Case Generator

Problem

During requirements reviews, test teams often need to turn feature specs, user stories, API docs, or acceptance criteria into executable test cases. Manual drafting tends to miss boundary values, permission differences, state transitions, and error paths, while hiding assumptions inside cases and causing repeated rework.

How It Works

The skill organizes output around test design methods:
- It identifies the test target, preconditions, input fields, business rules, permissions, and acceptance criteria;
- Applies boundary value analysis to numbers, dates, length, pagination, and amounts, decision tables to combination rules, and state transition testing to lifecycle flows;
- Covers valid inputs, invalid inputs, abnormal operations, network failures, concurrent submissions, and unauthorized access;
- Generates an .xlsx workbook by default with Test Cases, Test Analysis, and Requirement Questions sheets;
- Keeps case columns in a fixed order: Case ID, Priority, Test Type, Design Method, Case Title, Preconditions, Test Data, Steps, and Expected Result.

Boundaries

It is best suited for functional test case design from clear requirement materials, and does not replace interface automation, performance load testing, or security penetration testing. If the requirements lack role matrices, error codes, state rules, or supported ranges, the skill records the gaps in Requirement Questions instead of inventing hidden rules.