Gain insights into property-based testing with PropEr in Erlang. Delve into foundational principles, common frameworks, custom data generators, and applying testing in realistic projects for robust code validation.

Property Based Testing with PropEr in Erlang_468 x 60 copy.png

propert-based-testing.tar.gz

Erlang

Elixer

Erlang-Chap2

Elixir-Chap2

Erlang-Shell

erlang-user

elixir-user

elixir-shell

elrang-eunit

erlang-chap5-employee

elixir-cover_test

erlang-cover_test

erlang-chap10-databaseinit

erlang-chap10-user

elixir-chap10-user

erlang-chap10-shell

elixir-chap10-shell

erlang-chap10-dbsetup

elixir-chap10-dbSetup

erlang-chap5-templating

erlang-chap5-last

elixir-chap5-last

erlang-chap10-default

elixir-chap10-default

elixir-chap10-default-copy

Erlang-Chap2-copy

Elixir-Chap2-copy

Erlang-Shell-copy

elixir-shell-copy

erlang-default-force

elixir-default-force

erlang-test-shell

elxir-test-shell

Property-based testing relies on specifying some property of code, rather than unit tests which specify the expected output in response to some inputs. In this course, you’ll cover the concepts you need to get started, up to the point where you feel confident enough to use the most advanced features of PropEr with Erlang.

You’ll start smoothly with the basic and foundational principles of property-based testing. From there, you will cover some of the common frameworks, how to think in properties, how to write your own custom data generators, and more. You'll also see how you can use Property-Based Testing in a realistic project.

By the time you finish this course, you will be comfortable testing real-world applications using properties.

Property-Based Testing with PropEr in Erlang

# Abstract phase

PropEr divides the execution of a finite state machine test into two phases, one abstract and one real. The abstract phase is used to create a test scenario, using only the model and command generation callbacks, which are called to build out the sequence of calls that will later be applied to the system.

A graphical representation might look like this: 

The two big conceptual changes from stateful properties are for the initial state, now using both `initial_state` and `initial_state_data`, and an optional `weight` callback. Once the initial state and data are generated, the `StateName` callback is called, along with the optional `weight` function, to generate the next state transition and symbolic call to run.

That symbolic call is then passed, along with the data, to a `precondition` callback, which determines whether the call is valid or not. If the validation fails, PropEr tries again with a new generated command and state. Once a suitable command is found, the FSM generation moves forward.

The `next_state_data` function takes the command and the current state and has to return a new data structure. Then the whole process is repeated over and over until PropEr decides it has enough commands. 

# Real phase

Once a full sequence of commands is generated, PropEr will start applying them against the real system. This is what that looks like graphically:

Understand the execution model of FSM properties in both the abstract and real phases. 

How State Machine Properties Run

Understand the execution model of FSM properties in both the abstract and real phases.

Foundations of Property-Based Testing

Writing Properties

Thinking in Properties

Custom Generators

Responsible Testing

Properties-Driven Development

Shrinking

Targeted Properties

Stateful Properties

Case Study: Bookstore

State Machine Properties

Conclusion

How State Machine Properties Run

Abstract phase