A scenario is a succession of actions. We define a branching path as a way to create multiple tests from the same point. This allows easy compositionality of behaviors with minimal code sharing. The Tag allows to give meaningful identifiers to the branches. It is good practice to tag each case in a branch (it's not necessary, but since test names must be unique, at most one branch can remain unnamed, and even then it can create conflicting names.)

Unfolded scenario type

Continuation connector: execute a then b

Branching connector: creates two tests with different execution paths

Ends the test. Dump the state, returns unit

Transforms scenarios into tests

Arbitrary execution

Execute a function that does not modify the block, only the state

Execute a function that does not modify neither the block nor the state. Usually used for checks/asserts

fold f l folds f over l, fails on empty list

fold_tag f l folds f over l, l has a tag for each of its elements. Fails on empty list.

fold_tag_f f tag l folds f over l, tag returns a tag for each element of l. Fails on empty list.

unfold f l maps f over l, and runs them in order