org.specs2.specification.process

Default execution for specifications:

• concurrent by default
• using steps for synchronisation points

helper functions for executing fragments

Default selection for specification fragments:

• filter based on the name
• filter based on the tags
• filter based on previous execution

Functions for executing fragments.

The default execution model executes all examples concurrently and uses steps as "join" points

Fold function to compute the indentation of each fragment based on the presence of Tabs fragments

Compute the "level" of each fragment to be able to represent the whole specification as a tree.

In mutable specifications text fragments add one level to the following fragments, Otherwise should and can blocks create Start/End fragments indicating that the level should go up then down

This trait adds random execution constraints between examples.

As a result they will be executed in a random sequence

Selection function for Fragment processes

Compute the statistics for executed fragments

In memory store for statistics

Store the execution statistics.

The actual store might be on disk on in-memory

The Stats class store results for the number of:

• linked specifications
• examples (including linked examples)
• successes
• expectations
• failures
• errors
• pending
• skipped

The Stats class store results for the number of:

• successes
• expectations
• failures
• errors
• pending
• skipped

for each example

Concurrent execution of fragments in between steps