State Transition Test Design - QA Skill Library

Why this Skill

It turns this Skill's method into a quality input that can be executed, reviewed, and reused.

When you need State Transition Test Design candidates from state models, events, guard conditions, actions, roles, error transitions, and state-persistence evidence.
do not invent states or events, treat a static state diagram as runtime evidence, or claim all paths executed.
File presence, names, design declarations, and Eval configuration are not runtime evidence.
Mark unknowns unassessed, blocked, or pending clarification instead of filling them with convention.
Do not turn a method name, file presence, or candidate count into test execution, coverage, pass, or release evidence when scope or evidence is incomplete.

When to use

Use this Skill

When you need State Transition Test Design candidates from state models, events, guard conditions, actions, roles, error transitions, and state-persistence evidence.
When you need selection rationale, applicability constraints, evidence gaps, and the smallest validation action.
When inputs are incomplete but a bounded first pass can preserve blocked or unassessed boundaries.

Common pitfalls

Do not turn a method name, file presence, or candidate count into test execution, coverage, pass, or release evidence when scope or evidence is incomplete.
Do not fill in missing rules, thresholds, data, environments, or results from convention; preserve unassessed, blocked, and pending items.
Do not expand this specialist design or review into a complete strategy, full test cases, runtime execution, or a release decision.

Input

Minimum Input

Read prompts/state-transition-testing.md and provide the objective, scope, material, environment, and evidence.

Recommended Input

Project goal
Test scope
Constraints

Optional Context

Relevant code or configuration
Historical results
Logs and metrics

Output

The output follows this Skill's method and makes facts, assumptions, risks, and next steps explicit.

Judge the output value before installing

01Read prompts/state-transition-testing.md and provide the objective, scope, material, environment, and evidence.
02Complete known, missing, conflicting, stale, out_of_scope, and assumptions before findings.
03Record STT-## with state, event, precondition/guard, action, target state, reachability, source evidence, and validation method, source, evidence state, impact, owner, close condition, and validation.
04Preserve conflicts, unknown constraints, and open questions.

How It Works

01Read prompts/state-transition-testing.md and provide the objective, scope, material, environment, and evidence.
02Complete known, missing, conflicting, stale, out_of_scope, and assumptions before findings.
03Record STT-## with state, event, precondition/guard, action, target state, reachability, source evidence, and validation method, source, evidence state, impact, owner, close condition, and validation.
04Preserve conflicts, unknown constraints, and open questions.

Install & Quick Start

Install command / SHELL

npx skills add \
  https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/state-transition-testing
  -g

state-transition-testing.prompt

@skill state-transition-testing

Using the current project context, produce an actionable result following this Skill.

Additional context:
[Paste project context or requirement]

---
name: state-transition-testing
description: Use this skill when you need to derive test candidates for reachable, unreachable, and abnormal transitions from states, events, guards, and actions; triggers include 状态迁移测试 and state transition test design.
---

# State Transition Test Design

derive test candidates for reachable, unreachable, and abnormal transitions from states, events, guards, and actions. Produce STT-## findings. This Skill organizes traceable test-design candidates only; it does not execute tests or turn a design inventory into coverage, pass, or release evidence.

## When to Use

- When you need State Transition Test Design candidates from state models, events, guard conditions, actions, roles, error transitions, and state-persistence evidence.
- When you need selection rationale, applicability constraints, evidence gaps, and the smallest validation action.
- When inputs are incomplete but a bounded first pass can preserve blocked or unassessed boundaries.

Do not use it to execute tests, invent rules, replace a complete strategy, or accept risk for a Human.

## Output Format Options

- Use Markdown by default; use tables, JSON, or CSV only when explicitly requested or required by the delivery format.
- Separate static analysis, unexecuted work, evidence states, and Human decisions; keep items unassessed, blocked, or NOT_RUN when runtime evidence is absent.

## How to Use

1. Read prompts/state-transition-testing.md and provide the objective, scope, material, environment, and evidence.
2. Complete known, missing, conflicting, stale, out_of_scope, and assumptions before findings.
3. Record STT-## with state, event, precondition/guard, action, target state, reachability, source evidence, and validation method, source, evidence state, impact, owner, close condition, and validation.
4. Preserve conflicts, unknown constraints, and open questions.

## Core Constraints

- do not invent states or events, treat a static state diagram as runtime evidence, or claim all paths executed.
- File presence, names, design declarations, and Eval configuration are not runtime evidence.
- Mark unknowns unassessed, blocked, or pending clarification instead of filling them with convention.
- Do not edit requirements, code, test assets, or target systems.

## Pre-delivery Check

- [ ] Recorded the six-part input audit.
- [ ] Every STT-## has source, minimum evidence, impact/priority, owner role, close condition, and validation.
- [ ] Facts, inferences, recommendations, unexecuted work, and Human decisions remain separate.
- [ ] Findings are not full cases, execution results, coverage proof, or release claims.

## Reference Files

- Read evals/eval.yaml and matching cases for regression; configuration does not prove project results.
- Use evals/trigger-prompts.csv and evals/local-rules.json for trigger checks; missing skill.selection evidence is BLOCKED.

## Common Pitfalls

- Do not turn a method name, file presence, or candidate count into test execution, coverage, pass, or release evidence when scope or evidence is incomplete.
- Do not fill in missing rules, thresholds, data, environments, or results from convention; preserve unassessed, blocked, and pending items.
- Do not expand this specialist design or review into a complete strategy, full test cases, runtime execution, or a release decision.

## Best Practices

- Complete the six-part input audit before selecting the smallest traceable and verifiable finding scope.
- Keep the source, evidence state, impact/priority, owner role, close condition, validation method, and residual risk for every finding.
- Write validation suggestions as next actions; do not upgrade package structure, candidate counts, or local Eval configuration into real quality conclusions.