This exception class is used when an Action is transformed to a Task to avoid losing information
This trait provides simple a way to print out any object to the console:
This trait provides methods to catch exceptions and transform them into values which can be passed to further computations.
org.specs2.control.ExceptionsSpec for examples
This trait is used primarily to change the junit behavior depending on the execution environment
This trait provides utility methods for functions
This trait describes something which has a stackTrace with:
This trait is used to abuse method overloading and allow some of the methods in specs2 DSL to be applicable to various parameters.
Implementation of the StackTraceFilter trait with a list of include/exclude patterns
implicits and postfix ops are automatically mixed in specs2 specifications for convenience.
class holding a value to be evaluated lazily
This trait can be used to allow some function to be called with varargs, with values being evaluated lazily:
This class simply encapsulates a lazy value which will be only evaluated once
org.specs2.specification.process.RandomSequentialExecution for an example of use
Use this trait to disable the
pp method on objects
Syntactic sugar to execute an action a given number of times
This class represents values which are evaluated lazily and which may even be missing.
This trait filters an Exception stacktrace
Utility methods to determine the origin of the execution of the current code
This trait adds some utility methods to
This exception class is used to notify the user of instantiation errors
default filter for specs2 runs
Execute external commands
Factory object to build a stack trace filter from include/exclude expressions:
This filter doesn't do anything
Companion object to create properties with possibly no initial value
Utility object to show a parameter as used In particular this is useful to avoid warnings with ImplicitParameters
This implicit allows an Operation[result] to be used inside an example.
warn the user about something that is probably wrong on his side, this is not a specs2 bug, then fail to stop all further computations