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

# Finite state machines

**Finite state machines (FSM)** are, informally speaking, an abstraction describing specific stateful programs. The program can be in only one of the multiple known states at a time (such as a traffic light being red, yellow, or green). Transitions from one state to another are based on specific inputs or events. Within each state, the program may behave differently.

# Why use state machine properties

Let’s imagine a program that should take special measures, like forbidding some actions or enabling new features, depending on whether network connectivity is good, bad, or entirely unavailable. Testing such a program with stateful properties while keeping them deterministic would create a large number of possible cases. If there are six possible events and three possible states, we get at least eighteen possible combinations of calls versus states. We would have to do quite a bit of filtering in preconditions to hope to cover all kinds of transitions.

To help with this, PropEr provides finite state machine properties, which allow us to specifically model state machines. State names and transitions are made into first-class citizens, which allow us to adequately explore their expected transitions in a less cumbersome manner than would be required with regular stateful properties or example tests.

Finite-state properties are specifically helpful when users interact with the system while perceiving multiple states instead of knowing that the system has an internal state machine. To put it another way, state machine properties are for when the model itself is a state machine, instead of the system. If there are no specific, discernible states for the user, and therefore no specific, discernible states for the model, then regular stateful properties are more appropriate.

Get introduced to state machine properties and why there is a need to use them. 

Introduction to State Machine Properties

Get introduced to state machine properties and why there is a need to use them.

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

Introduction to State Machine Properties

Finite state machines