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 can be mixed-in a specification to allow examples to have all of their expectations being evaluated (unless the example body throws an exception of course).
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
Decorated creation where the body of the example can be surrounded with a given context if necessary
Default implementation for the example factory trait just creating an Example object
A Example is:
This trait defines methods for creating Examples.
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
A Fixture can be implicitly passed to a set of examples taking a function as an input.
For each created example use a given after method
Formatting for Text fragments
Set of fragments which can be used for formatting
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 trait provides function to create specification Fragments:
This trait post-process fragments.
Fragments can be chained with the ^ method
This trait can be used to standardize names for groups of examples in an acceptance specification.
This trait can be used to standardize names for groups of examples in an acceptance specification.
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
encapsulation of the linking behaviour
This class provides functionalities for manipulating Markdown links
This trait ca be used to deactivate all automatic conversions to examples
This trait deactivates the implicit on Strings which is used to create examples with !
This trait can be used to deactivate the Boolean conversions to fragments and examples
Use this trait to deactivate the Contexts implicits
This trait can be used to deactivate the DataTable conversions to fragments and examples
This trait can be used to deactivate implicits for building fragments
This trait can be used to deactivate the MatchResult conversions to fragments and examples
This trait can be used to deactivate the Result conversions to fragments and examples
This trait can be used to deactivate implicits for ~ and ~/ operators on strings
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
This class is used to evaluate a Context as a sequence of results by side-effects.
Marker trait that is used to create a new scope with variables and implicitly converted to a Success in a mutable Specification
Snippets of code can be extracted from interpolated specification strings.
End of a specification.
Identification information for a specification
Name declaration for a specification
Start of a specification.
additional methods to include other specifications or Fragments
This trait models "what happens" before a fragment is created in terms of side-effects.
Allow to use fragments inside interpolated strings starting with s2 in order to build the specification content
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.
This trait can be used when it is not desirable to use the AllExpectations trait, that is, when the specification examples must be executed concurrently and not isolated.
This trait is a context which will use the results provided by the class inheriting that trait.
The tags trait allows the creation of Tags fragments in a Specification
Free text, describing the system to specify
Utility methods for fragments
methods for creating SpecificationStructure instances from fragments
Those standard Fragments are used to format the specification text:
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\