nw-pbt-stateful

Stateful property-based testing validates systems with mutable state by using a model-driven approach to generate and verify sequences of operations. You configure a simplified model, define commands, and run a two-phase workflow to check postconditions.

Two-phase execution in model-based testing separates operation generation from concrete execution. Phase 1 generates a sequence of commands from a simplified model, and phase 2 executes them against the system to ensure resulting state aligns with model postconditions.

Yes, stateful property-based testing applies to databases, APIs, caches, queues, and protocols where operations evolve state over time. It supports command patterns like CRUD, resource lifecycle, and transaction workflows to validate these mutable systems.

Yes, stateful property-based testing provides linearizability testing guidance to reason about concurrency. It helps uncover bugs that arise from stateful interactions by validating that concurrent operations adhere to the expected model behavior.

You can debug failing stateful tests and avoid anti-patterns by following the model-driven workflow, which ensures postconditions align with the simplified model. It also provides specific guidance on scalability and common stateful testing anti-patterns.