Stateful Scenarios: Mockoon vs Powerduck
Short answer: Both support stateful behavior, but the source differs. A dedicated mock sequences the states you design; a studio keeps the state tied to the contract and the tests, so the flow the agent exercises is the flow the spec describes. The first is authored; the second is derived.
What authored scenarios provide
Precise control over a sequence: a create, a list, a token that expires. They are the right tool for bespoke behavior.
What contract-tied scenarios provide
| Property | Authored | Contract-tied |
|---|---|---|
| State source | Mock logic | Spec and tests |
| Validity | As designed | By construction |
| On change | Update scenario | With spec |
| Drift | Common | Rare |
Why the tie matters
A stateful mock that is separate from the tests can diverge from the real flow. A contract-tied scenario keeps the agent's path and the described path aligned.
The decision rule
Authored scenarios are right for bespoke sequences. Contract-tied scenarios are the lower-maintenance path for a changing API.
This is part of the Powerduck vs Mockoon comparison. Finish with record vs spec.