Model-Based Test Design

Derive test-path candidates from sourced behavior, state, or process models. Produce MBT-## design candidates within the evidence boundary; do not execute tests or claim coverage or pass results.

When to Use

• Analyze behavior models, states or nodes, events, path constraints, model versions, and existing execution evidence.
• Preserve selection rationale, evidence gaps, priority, and validation actions.
• Inputs are incomplete but a bounded first pass can mark items unassessed or blocked.

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