An Action is similar to a Step but can be executed concurrently with other examples.
The After trait can be inherited by classes representing a context where an action must be executing after the main executable action
For each created example use a given After context
apply an After context to each Example
For each created example use a given after method
This trait provides integrated analysis method for a scala project
Apply a Context to a sequence of fragments containing examples.
The Around trait can be inherited by classes which will execute some code inside the around method provided by the context.
For each created example use a given Around context
apply an Around context to each Example
For each created example use a given around method
The AroundOutside trait can be inherited by classes which will execute some code inside a given context, with a function using that context and actions before and after if necessary.
A Base specification contains the minimum elements for a Specification
The Before trait can be inherited by classes representing a context where an action must be executing before the main executable action
The BeforeAfter trait allows to declare before and after actions to execute before and after an Example
The BeforeAfter trait allows to declare before, around and after actions
For each created example use a given BeforeAfterAround context
apply a BeforeAfterAround context to each Example
For each created example use a given before/after method
For each created example use a given BeforeAfter context
apply a BeforeAfter context to each Example
For each created example use a given before/after method
For each created example use a given Before context
apply a Before context to each Example
For each created example use a given after method
generic trait for Before, After, Around
This trait is only used when we wish to write after actions in unit specifications like this
A Example is:
The Executed Fragments represent pieces of a Specification which have already been executed to provide a Result
This executed Fragment is used when no text must be displayed (for the successful execution of an Action for example)
A specification with a name and all of its fragments already executed
The Executing Fragment trait represent a Fragment being executed.
a specification with a name and a sequence of fragments being executed
embed an already executed Fragment
The FormMarkup embeds the description of a form as text or as Xml
Set of fragments which can be used for formatting
Allow a Form to be inserted among Fragments as a Text Fragment Allow a Form to be used as an example body and return a Result automatically
A Fragment is a piece of a specification.
This trait executes Fragments
A Fragments object is a list of fragments with a SpecStart and a SpecEnd
This step can start a sequence of Given / When / Then.
The HtmlLink class represents a link in a specification with an identifier (either a spec name, or a string) and link elements.
embed an executing Fragment into a function to execute it on demand
The Outside trait can be inherited by classes which will execute some code inside the outside method provided by the context.
embed an executed Fragment into a promise
A Regular expression step which takes a text and extracts meaningful values according to a regular expression:
This trait provides building blocks to create steps and examples from regular expression.
Marker trait that is used to create a new scope with variables and implicitly converted to a Success in a mutable Specification
End of a specification.
Start of a specification.
additional methods to include other specifications or Fragments
The structure of a Specification is simply defined as a sequence of fragments
The Stats class store results for the number of: - successes - expectations - failures - errors - pending - skipped
An Step creates a fragment that will either return an Error Result if there is an exception or a Success.
The tags trait allows the creation of Tags fragments in a Specification
Free text, describing the system to specify
This step define checks in a sequence of Given / When / Then.
This step define conditions in a sequence of Given / When / Then.
Utility methods for fragments
The Stats class store results for the number of: - successes - expectations - failures - errors - pending - skipped
Those fragments are used to tag other fragments in a specification\