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

# The main function

It’s now time to take these well-tested bits and integrate them. Fortunately for us, we care about unit tests, so we can just throw everything together quickly and consider our job done. Let's take a look at the main functions and see how that could be done.

The email client is not implemented since it is also out of our scope for now. We’ll stick with a simple `io:format/2` call to stand in for the actual email client handling. We just need to package the program to be run.

# Code

The main function is defined in the `src/bday.erl` file in the following code. Take a look at it there.

To package the program we run the command `rebar3 escriptize`. 

The script is generated in the `_build/default/bin` directory. The program can now be run, as long as the sample CSV file has full CRLF line terminations. 

> **Remember:** Ensure one of the employees in the sample database in `priv/db.csv` has their birthday today (whatever day it is when you are reading this) for the program to output anything. To run the packaged program, run the command: `_build/default/bin/bday priv/db.csv`. \
The format of the date is `YYYY/MM/DD`.


Put all the modules of the previous lessons together to have a complete runnable and testable application. 

Putting It All Together

Put all the modules of the previous lessons together to have a complete runnable and testable application.

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

Putting It All Together

The main function