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.

48 stars 10 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill state-transition-testing
Manual install
git 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-testing

Personal 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
Read the full skill on GitHub

Details

Skill name
state-transition-testing
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

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.