State Transition Testing
Design tests from state machine models to verify correct transitions, guard conditions, and invalid state handling. Use for workflows, UI flows, protocols, and stateful components.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill state-transition-testinggit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/qa-engineer/functional-testing/skills/state-transition-testing ~/.claude/skills/state-transition-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# State Transition Testing Model system behavior as finite state machines and derive tests that verify every valid transition fires correctly, every guard condition is enforced, and every invalid transition is properly rejected. ## Context You are a senior QA engineer designing state transition tests for $ARGUMENTS. This black-box technique is essential for any component with distinct states and event-driven behavior. ## Domain Context - **ISTQB Foundation Syllabus (4.2.4)**: State transition testing is a formal black-box technique. Coverage levels range from 0-switch (all transitions) to N-switch (transition sequences of length N) - **ISO/IEC 25010**: Functional correctness requires that all specified state transitions produce correct outputs and that unspecified transitions are handled safely - **UML State Machine Diagrams** (OMG UML 2.5): Provide standard notation for states, transitions, guards, actions, and composite states - **Mealy vs. Moore machines**: Outputs depend on transition (Mealy) or state (Moore) — this distinction affects where to place assertions ## Instructions 1. **Model the state machine**: Identify all states, events/triggers, guard conditions, actions, and transitions. Draw the state transition diagram or build a state transition table. Include initial state, terminal states, and error/recovery states
Details
- Skill name
state-transition-testing- Repository
- sethdford/claude-skills
- Path
qa-engineer/functional-testing/skills/state-transition-testing/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the State Transition Testing skill do?
Design tests from state machine models to verify correct transitions, guard conditions, and invalid state handling. Use for workflows, UI flows, protocols, and stateful components.
How do I install the State Transition Testing skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is State Transition Testing popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Stress Test Plan
48sethdford/claude-skills
Expert approach to stress-test-plan in performance testing. Use when working with .
Spike Test Plan
48sethdford/claude-skills
Expert approach to spike-test-plan in performance testing. Use when working with .
TDD Workflow
48sethdford/claude-skills
Red-Green-Refactor cycle for test-first development. Write failing test, implement minimal code, refactor safely. Use when developing new features or fixing bugs in test-driven projects.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.