st-test-designer

Generates state transition test designs, test cases, and bug reports for EShop features.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/DuyITLOR/group05_eshop --skill st-test-designer-duyitlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: st-test-designer
Source: https://github.com/DuyITLOR/group05_eshop/tree/main/.claude/skills/st-test-designer
Command: npx skills add https://github.com/DuyITLOR/group05_eshop --skill st-test-designer-duyitlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing black-box test cases for stateful features (login lockout, cart lifecycle, order status, OTP flows) is error-prone when done ad hoc. This Skill applies the State Transition Testing technique systematically, producing a complete, traceable test artifact set from the EShop requirements specification. ## Core Features & Use Cases - Four-step guided workflow: suggests applicable FRs from README.md, builds a state model (states, actions, State×Actions table, mermaid diagram), generates End-to-End test cases as individual markdown files, then executes them and writes bug reports — pausing for user confirmation at each step. - Strict modeling conventions: full state names (no S0/S1), mermaid stateDiagram-v2 charts, C1 tables with exactly |States|×|Actions| rows, and bidirectional Test Case ↔ Bug traceability. - Use Case: Ask it to apply state transition testing to FR-07 (shopping cart); it produces a Test Design document, TC-CART-E2E-xx test case files, bug reports for failures, and a traceability matrix ready for coursework submission. ## Quick Start Ask the agent to apply state transition testing to FR-07 of the EShop spec and confirm each step as it presents the design, test cases, and execution results.

Frequently Asked Questions about st-test-designer

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

FAQPage Schema
How do I design state transition test cases for a login lockout feature?▼

Model the failed-attempt counter and 30-second lock as states, then build a State×Actions table covering valid and invalid transitions. This Skill generates that design plus End-to-End test cases automatically from the FR-02 specification.

What is state transition testing and when should I use it?▼

State transition testing is a black-box technique for features whose behavior depends on current state plus events, such as order status flows, OTP lifecycles, or cart dialogs. It is unsuitable for stateless validations like pure input format checks.

Which EShop requirements are suitable for state transition testing?▼

The Skill recommends FR-07 (cart lifecycle), FR-02 (login lockout), FR-03 (two-step password reset with OTP), FR-10 (order status machine), and FR-08 (checkout), because each has history-dependent behavior or multi-step flows.

Does the skill execute the test cases against the real system?▼

Yes, in step 3 it runs the actual frontend on port 5173 and backend on port 3000, records Actual results and Status, and writes one bug report file per failed case. You can also skip execution, leaving Status as Not Run.

What output files does the state transition test workflow produce?▼

It produces a Test Design markdown with mermaid diagrams and the C1 table, one markdown file per End-to-End test case, bug report files for failures, and a traceability matrix linking transitions, test cases, results, and bugs.