org.specs2.matcher

Inherit this trait to provide a Matcher where both the actual and the expected values can be adapted with a function.

This matcher always matches any value of type T

This trait allows to write expressions like

1 must be equalTo(1)

This trait provides matchers which are applicable to any type of value

Equality Matcher

ValueCheck for a typed expected value. It uses the BeTypedEqualTo matcher

ValueCheck for an untyped expected value. It uses the BeEqualTo matcher

Matcher for a boolean value which must be true

Typed equality Matcher with fallback comparison results

transient class allowing the creation of a delta

This trait provides implicit definitions and types to create DataTables.

A DataTable has a header defining column names and rows holding values. It is possible to apply a function taking the row values and returning a MatchResult.

A TableHeader is defined by separating the column names with '|': "a" | "b" | "c"

A DataRow is defined by separating the row values with '!': 1 ! 2 ! 3

Note that the '!' method can conflict with the creation of Examples when the value is a string. In that case it is possible to use the '!!! method to disambiguate:

"1" !! "2" ! "3"

In that case the first column of the header can also be defined with '||' for pure symmetry reasons:

"a" || "b" | "c" "1" !! "2" ! "3"

Matchers for the Either datatype

This trait adds the possibility to retry a given matcher until it succeeds.

This was contributed by @robey (http://robey.lag.net)

These matchers can be used to check if exceptions are thrown or not

The Expectable class models anything which can be checked by applying a Matcher

It stores a value which is only evaluated when necessary and an optional additional description for that value.

The Expectable object is responsible for creating its own description, based on the value toString method and and an additional description.

Factory methods for creating Expectables

This trait provides implicit definitions to transform any value into an Expectable

Base trait to create expectations

Matchers for Maps

this class allows to throw a match failure result in an Exception

this class allows to throw a pending result in an Exception

Result of a Match.

A MatchResult contains several information about a match on an expectable:

• the expectable value, to allow the chaining of matches
• a pair of messages ok message / ko message to allow the easy creation of the negation of a match

A MatchResult can be transformed to a simple Result object to be the body of an Example.

There are different kinds of MatchResults, some of them being only created to support English-like combination of Matchers:

1 must be equalTo(1) and not be equalTo(2)

In an Expectation like the one above, there is a left to right evaluation:

1. be is a NeutralMatcher, returning a NeutralMatch doing nothing yet, just storing the expectable

2. equalTo(1) is a real Matcher which is applied to the NeutralMatch MatchResult thanks to an implicit definition in the BeHaveAnyMatchers trait. This yields a MatchSuccess result

3. not creates a NotMatcher and can be and-ed with the previous MatchSuccess to yield a AndMatch(MatchSuccess, NotMatch), with NotMatch being the result of applying the NotMatcher to the expectable. This AndMatch is evaluated to create a AndNotMatch(MatchSuccess, MatchSkip)

   Basically this is like forming an evaluation structure which will be resolved when the next 'real' matcher will arrive

4. the AndNotMatch get nows it be method called with the equalTo Matcher. This results in equalTo being applied to the AndNotMatch, effectively doing: MatchSuccess and MatchSkip.apply(equalTo(2).not), which is MatchSuccess and expectable.applyMatcher(equalTo(2).not) which is MatchSuccess

Utility functions for MatchResult.

A MatchResult is a Functor where the fmap function acts on the embedded Expectable value (which itself is a Functor)

This trait provides logical operators to combine match results where potentially a MatchResult expression throws an Exception, either because it is an error or because it is a ThrownExpectation

Implicit conversions for MatchResults

this trait allows to fill-in stack traces on match results for precise location

this class allows to throw a skipped match result in an Exception

The signature of this class constructor is unusual, with a useless implicit parameter.

This is actually here to avoid overloading conflicts with the apply method in the companion object

The Matcher trait is the base trait for any Matcher.

This trait can be extended to provide an appropriate apply method that will check an expectable value a: Expectable[T].

The result of a match is a MatchResult object (@see MatchResult).

Matchers can be composed.

Implementation notes:

• the parameter to the apply method must be a by-name parameter. This allows some values to be evaluated only when necessary.

• However in the implementation of the apply function, it must be taken care of not evaluating the parameter twice. Assigning it to a val is the solution to this issue.

This trait provides 'zip' operators to create matchers on tuples based on "zipped" matchers on fields

Generation code for the MatcherZipOperators trait

Trait aggregating the most common specs2 matchers

This trait provides implicit definitions from MatchResults and Booleans to Results.

It also allows to:

• create matchers from functions
• create matchers for seqs and sets from single matchers

This kind of expectable can be followed by the verb must to apply a matcher:

1 must beEqualTo(1)

For convenience, several mustMatcher methods have also been defined as shortcuts to equivalent:

a must matcher

This trait provides implicit definitions to transform any value into a MustExpectable

This trait provides implicit definitions to transform any value into a MustExpectable, throwing exceptions when a match fails

This special matcher always return a NeutralMatch MatchResult (an implicit Success)

This matcher never matches any value of type T

this trait doesn't fill-in stack traces

code generation for the NoMatcherZipOperatorsImplicits trait

This trait can be used to remove aka and must methods on any value

This trait can be used to remove aka and should methods on any value

This trait can be used to cancel the effect of thrown expectations.

For example it can be mixed-in a mutable.Specification so that no exception is thrown on failure

This trait can be used to suppress the TypedEqual implicit

This special matcher always return a NotMatch MatchResult. It will negate the next match applied to it.

Matchers for Numerical values

Matchers for Operation values

Matchers for Options

class representing a numeric range

Matchers for Results

Those definitions help specifying the result messages for matchers

This trait represents any Scope that is used to enclose expectations which might be thrown

This kind of expectable can be followed by the verb should to apply a matcher:

1 should beEqualTo(1)

For convenience, several shouldMatcher methods have also been defined as shortcuts to equivalent:

a should matcher

This trait provides implicit definitions to transform any value into a ShouldExpectable