Introduction

The unit test is the lowest common denominator. We can use them, but they are cumbersome and they only peek once into the fabric of our work. A better solution for many tasks, namely Property Based Testing exists for Erlang. This post is an example of how to use the statem type of test, mainly because there are so few of these out there. The outset is this: We will randomly generate operations on a priority queue and then validate that these operations are correct according to a simpler model.

Det skal være nemt for folk at slukke for strømmen efter sig, når de går. I dag har den adfærd tre udfordringer:

1. Man skal gå rundt til de enkelte enheder og slukke for dem.

2. Man skal overveje hvilke enheder der må slukkes og hvilke der skal stå tændt hele tiden.

3. Hvis man slukker en enhed ved at bruge enhedens egen funktionalitet til dette, sker det tit at enhedens strømforsyning forbliver tændt. Meget tit.

Disse tre problemer kan løses således:

A Hasse diagram generated in Mathematica.

Having realised Mr Simon Shine's attempt to ruin my good name by turning it into a drinking game, I have decided to return the favour and give him some of his own medicine. Although, I must admit, I did not realise vegetarians were allowed to have fun. Aren't they supposed to walk around constantly feeling bad for the animals that died? And what about the yeast in beer? Isn't that A LIVE?!

Any way, the drinking rules with Simon Shine is very simple and straight forward, even if it is played over numerous days.