Writing Stateful Properties

Getting started

We’ve seen that stateless properties all follow a pretty similar structure. The layout of code may vary from project to project, but overall, most test suites do share a separation between properties, generators, and helper functions. When it comes to stateful properties, there is far less of a standard. Some people put properties in one file, models in another one, with helper functions and wrappers around the actual system in a third module. Other developers prefer to have everything in one spot.

We’ll stick to keeping the properties and model in one file. With basic properties, we can make use of the rebar3 plugin’s templating facilities to get the file we need within any standard Erlang project. The command is:

rebar3 new proper_statem base

File structure

The generated file contains the prop_base module, a test suite that is divided into two sections:

1. Section for the stateful property we’ll want to execute.
2. Section for the model, which is a mix of callbacks and generators.

Properties

Let’s start by looking at the property.