← ClaudeAtlas

model-based-test-graph-authorlisted

Use when a complex stateful flow (checkout, onboarding, multi-step wizard) needs systematic model-based coverage that ad-hoc tests miss. Builds a state-machine model, checks it is complete, picks a coverage criterion, generates covering paths and turns them into a curated test suite.
testland/qa · ★ 13 · AI & Automation · score 80
Install: claude install-skill testland/qa
# model-based-test-graph-author ## Overview Per [mbt-wiki][mbt]: [mbt]: https://en.wikipedia.org/wiki/Model-based_testing > "**Model-based testing** is an approach to testing that > leverages model-based design for designing and possibly executing > tests. A model typically represents either the desired behavior > of a system under test or testing strategies themselves." > "Often the model is translated to or interpreted as a > finite-state automaton or a state transition system." ([mbt-wiki][mbt]) The state machine is the artifact; test paths are derived from it. This skill produces the state-machine model (input to MBT tools or AI test generators). ## When to use - A complex stateful flow exists (multi-step wizard, checkout funnel, onboarding flow, payment state machine). - Ad-hoc test authoring keeps missing edge cases. - The team wants exhaustive transition coverage that manual tests can't provide. ## How to use 1. **Identify the state space** - list every state and every transition (event + guard + action) of one flow. One model per flow, never one giant model for the whole app. 2. **Author the model** in a portable YAML format - states carry `initial` / `final` flags; transitions carry `from` / `to` / `event` / `guard` / `action`. 3. **Validate the model** - every transition references a real state, every state is reachable from the initial state, and every state can reach a final state. Validator + coverage-criteria detail in [referen