nw-pbt-stateful

Stateful property-based testing validates systems with mutable state by encoding expectations as models and generating operation sequences. You need it for databases, APIs, caches, queues, state machines, and protocols to verify sequential behavior.

Model-based testing for stateful APIs uses a two-phase execution model. You define commands with explicit preconditions, state transitions, and postconditions to generate operation sequences, then execute them concretely against the real system to verify correctness.

Yes, stateful property-based testing applies to databases, caches, queues, and file systems without external dependencies. It operates by generating symbolic references and verifying state transitions internally against your defined model.

The best way to structure commands for stateful property-based testing is using the command design pattern. Define explicit preconditions, execution logic, state transitions, and postconditions to ensure correctness and create reusable test models.

Two-phase execution in stateful model-based testing separates test generation from concrete execution. The first phase generates operation sequences with symbolic references, and the second phase executes them against the real system to validate postconditions.

Common anti-patterns in stateful test models involve neglecting explicit preconditions, mishandling state transitions, and ignoring symbolic references. Following best practices ensures correct operation sequence generation and reusable models across databases and APIs.