Trait that provides a domain specific language (DSL) for expressing assertions in tests
using the word must
.
For example, if you mix Matchers
into
a suite class, you can write an equality assertion in that suite like this:
result must equal (3)
Here result
is a variable, and can be of any type. If the object is an
Int
with the value 3, execution will continue (i.e., the expression will result
in the unit value, ()
). Otherwise, a TestFailedException
will be thrown with a detail message that explains the problem, such as "7 did not equal 3"
.
This TestFailedException
will cause the test to fail.
Here is a table of contents for this documentation:
Trait must.Matchers
is an alternative to should.Matchers
that provides the exact same
meaning, syntax, and behavior as should.Matchers
, but uses the verb must
instead of should
.
The two traits differ only in the English semantics of the verb: should
is informal, making the code feel like conversation between the writer and the reader; must
is more formal, making the code feel more like
a written specification.
== Checking equality with matchers ==
ScalaTest matchers provides five different ways to check equality, each designed to address a different need. They are:
result must equal (3) // can customize equality result must === (3) // can customize equality and enforce type constraints result must be (3) // cannot customize equality, so fastest to compile result mustEqual 3 // can customize equality, no parentheses required result mustBe 3 // cannot customize equality, so fastest to compile, no parentheses required
The “left
must
equal
(right)
” syntax requires an
org.scalactic.Equality[L]
to be provided (either implicitly or explicitly), where
L
is the left-hand type on which must
is invoked. In the "left
must
equal
(right)
" case,
for example, L
is the type of left
. Thus if left
is type Int
, the "left
must
equal
(right)
"
statement would require an Equality[Int]
.
By default, an implicit Equality[T]
instance is available for any type T
, in which equality is implemented
by simply invoking ==
on the left
value, passing in the right
value, with special treatment for arrays. If either left
or right
is an array, deep
will be invoked on it before comparing with ==. Thus, the following expression
will yield false, because Array
's equals
method compares object identity:
Array(1, 2) == Array(1, 2) // yields false
The next expression will by default not result in a TestFailedException
, because default Equality[Array[Int]]
compares
the two arrays structurally, taking into consideration the equality of the array's contents:
Array(1, 2) must equal (Array(1, 2)) // succeeds (i.e., does not throw TestFailedException)
If you ever do want to verify that two arrays are actually the same object (have the same identity), you can use the
be theSameInstanceAs
syntax, described below.
You can customize the meaning of equality for a type when using "must
equal
," "must
===
,"
or mustEqual
syntax by defining implicit Equality
instances that will be used instead of default Equality
.
You might do this to normalize types before comparing them with ==
, for instance, or to avoid calling the ==
method entirely,
such as if you want to compare Double
s with a tolerance.
For an example, see the main documentation of trait org.scalactic.Equality
.
You can always supply implicit parameters explicitly, but in the case of implicit parameters of type Equality[T]
, Scalactic provides a
simple "explictly" DSL. For example, here's how you could explicitly supply an Equality[String]
instance that normalizes both left and right
sides (which must be strings), by transforming them to lowercase:
scala> import org.scalatest.matchers.must.Matchers._ import org.scalatest.matchers.must.Matchers._ scala> import org.scalactic.Explicitly._ import org.scalactic.Explicitly._ scala> import org.scalactic.StringNormalizations._ import org.scalactic.StringNormalizations._ scala> "Hi" must equal ("hi") (after being lowerCased)
The after
being
lowerCased
expression results in an Equality[String]
, which is then passed
explicitly as the second curried parameter to equal
. For more information on the explictly DSL, see the main documentation
for trait org.scalactic.Explicitly
.
The "must
be
" and mustBe
syntax do not take an Equality[T]
and can therefore not be customized.
They always use the default approach to equality described above. As a result, "must
be
" and mustBe
will
likely be the fastest-compiling matcher syntax for equality comparisons, since the compiler need not search for
an implicit Equality[T]
each time.
The must
===
syntax (and its complement, must
!==
) can be used to enforce type
constraints at compile-time between the left and right sides of the equality comparison. Here's an example:
scala> import org.scalatest.matchers.must.Matchers._ import org.scalatest.matchers.must.Matchers._ scala> import org.scalactic.TypeCheckedTripleEquals._ import org.scalactic.TypeCheckedTripleEquals._ scala> Some(2) must === (2) <console>:17: error: types Some[Int] and Int do not adhere to the equality constraint selected for the === and !== operators; the missing implicit parameter is of type org.scalactic.CanEqual[Some[Int],Int] Some(2) must === (2) ^
By default, the "Some(2)
must
===
(2)
" statement would fail at runtime. By mixing in
the equality constraints provided by TypeCheckedTripleEquals
, however, the statement fails to compile. For more information
and examples, see the main documentation for trait org.scalactic.TypeCheckedTripleEquals
.
== Checking size and length ==
You can check the size or length of any type of object for which it makes sense. Here's how checking for length looks:
result must have length 3
Size is similar:
result must have size 10
The length
syntax can be used with String
, Array
, any scala.collection.GenSeq
,
any java.util.List
, and any type T
for which an implicit Length[T]
type class is
available in scope.
Similarly, the size
syntax can be used with Array
, any scala.collection.GenTraversable
,
any java.util.Collection
, any java.util.Map
, and any type T
for which an implicit Size[T]
type class is
available in scope. You can enable the length
or size
syntax for your own arbitrary types, therefore,
by defining Length
or Size
type
classes for those types.
In addition, the length
syntax can be used with any object that has a field or method named length
or a method named getLength
. Similarly, the size
syntax can be used with any
object that has a field or method named size
or a method named getSize
.
The type of a length
or size
field, or return type of a method, must be either Int
or Long
. Any such method must take no parameters. (The Scala compiler will ensure at compile time that
the object on which must
is being invoked has the appropriate structure.)
== Checking strings ==
You can check for whether a string starts with, ends with, or includes a substring like this:
string must startWith ("Hello") string must endWith ("world") string must include ("seven")
You can check for whether a string starts with, ends with, or includes a regular expression, like this:
string must startWith regex "Hel*o" string must endWith regex "wo.ld" string must include regex "wo.ld"
And you can check whether a string fully matches a regular expression, like this:
string must fullyMatch regex """(-)?(\d+)(\.\d*)?"""
The regular expression passed following the regex
token can be either a String
or a scala.util.matching.Regex
.
With the startWith
, endWith
, include
, and fullyMatch
tokens can also be used with an optional specification of required groups, like this:
"abbccxxx" must startWith regex ("a(b*)(c*)" withGroups ("bb", "cc")) "xxxabbcc" must endWith regex ("a(b*)(c*)" withGroups ("bb", "cc")) "xxxabbccxxx" must include regex ("a(b*)(c*)" withGroups ("bb", "cc")) "abbcc" must fullyMatch regex ("a(b*)(c*)" withGroups ("bb", "cc"))
You can check whether a string is empty with empty
:
s mustBe empty
You can also use most of ScalaTest's matcher syntax for collections on String
by
treating the String
s as collections of characters. For examples, see the
String
s and Array
s as collections section below.
== Greater and less than ==
You can check whether any type for which an implicit Ordering[T]
is available
is greater than, less than, greater than or equal, or less
than or equal to a value of type T
. The syntax is:
one must be < 7 one must be > 0 one must be <= 7 one must be >= 0
== Checking Boolean
properties with be
==
If an object has a method that takes no parameters and returns boolean, you can check
it by placing a Symbol
(after be
) that specifies the name
of the method (excluding an optional prefix of "is
"). A symbol literal
in Scala begins with a tick mark and ends at the first non-identifier character. Thus,
'traversableAgain
results in a Symbol
object at runtime, as does
'completed
and 'file
. Here's an example:
iter mustBe 'traversableAgain
Given this code, ScalaTest will use reflection to look on the object referenced from
emptySet
for a method that takes no parameters and results in Boolean
,
with either the name empty
or isEmpty
. If found, it will invoke
that method. If the method returns true
, execution will continue. But if it returns
false
, a TestFailedException
will be thrown that will contain a detail message, such as:
non-empty iterator was not traversableAgain
This be
syntax can be used with any reference (AnyRef
) type. If the object does
not have an appropriately named predicate method, you'll get a TestFailedException
at runtime with a detailed message that explains the problem.
(For the details on how a field or method is selected during this
process, see the documentation for BeWord
.)
If you think it reads better, you can optionally put a
or an
after
be
. For example, java.io.File
has two predicate methods,
isFile
and isDirectory
. Thus with a File
object
named temp
, you could write:
temp must be a 'file
Or, given java.awt.event.KeyEvent
has a method isActionKey
that takes
no arguments and returns Boolean
, you could assert that a KeyEvent
is
an action key with:
keyEvent must be an 'actionKey
If you prefer to check Boolean
properties in a type-safe manner, you can use a BePropertyMatcher
.
This would allow you to write expressions such as:
xs mustBe traversableAgain temp must be a file keyEvent must be an actionKey
These expressions would fail to compile if must
is used on an inappropriate type, as determined
by the type parameter of the BePropertyMatcher
being used. (For example, file
in this example
would likely be of type BePropertyMatcher[java.io.File]
. If used with an appropriate type, such an expression will compile
and at run time the Boolean
property method or field will be accessed directly; i.e., no reflection will be used.
See the documentation for BePropertyMatcher
for more information.
== Using custom BeMatchers
==
If you want to create a new way of using be
, which doesn't map to an actual property on the
type you care about, you can create a BeMatcher
. You could use this, for example, to create BeMatcher[Int]
called odd
, which would match any odd Int
, and even
, which would match
any even Int
.
Given this pair of BeMatcher
s, you could check whether an Int
was odd or even with expressions like:
num mustBe odd num must not be even
For more information, see the documentation for BeMatcher
.
== Checking object identity ==
If you need to check that two references refer to the exact same object, you can write:
ref1 must be theSameInstanceAs ref2
== Checking an object's class ==
If you need to check that an object is an instance of a particular class or trait, you can supply the type to
“be
a
” or “be
an
”:
result1 mustBe a [Tiger] result1 must not be an [Orangutan]
Because type parameters are erased on the JVM, we recommend you insert an underscore for any type parameters
when using this syntax. Both of the following test only that the result is an instance of List[_]
, because at
runtime the type parameter has been erased:
result mustBe a [List[_]] // recommended result mustBe a [List[Fruit]] // discouraged
== Checking numbers against a range ==
Often you may want to check whether a number is within a
range. You can do that using the +-
operator, like this:
sevenDotOh must equal (6.9 +- 0.2) sevenDotOh must === (6.9 +- 0.2) sevenDotOh must be (6.9 +- 0.2) sevenDotOh mustEqual 6.9 +- 0.2 sevenDotOh mustBe 6.9 +- 0.2
Any of these expressions will cause a TestFailedException
to be thrown if the floating point
value, sevenDotOh
is outside the range 6.7
to 7.1
.
You can use +-
with any type T
for which an implicit Numeric[T]
exists, such as integral types:
seven must equal (6 +- 2) seven must === (6 +- 2) seven must be (6 +- 2) seven mustEqual 6 +- 2 seven mustBe 6 +- 2
== Checking for emptiness ==
You can check whether an object is "empty", like this:
traversable mustBe empty javaMap must not be empty
The empty
token can be used with any type L
for which an implicit Emptiness[L]
exists.
The Emptiness
companion object provides implicits for GenTraversable[E]
, java.util.Collection[E]
,
java.util.Map[K, V]
, String
, Array[E]
, and Option[E]
. In addition, the
Emptiness
companion object provides structural implicits for types that declare an isEmpty
method that
returns a Boolean
. Here are some examples:
scala> import org.scalatest.matchers.must.Matchers._ import org.scalatest.matchers.must.Matchers._ scala> List.empty mustBe empty scala> None mustBe empty scala> Some(1) must not be empty scala> "" mustBe empty scala> new java.util.HashMap[Int, Int] mustBe empty scala> new { def isEmpty = true} mustBe empty scala> Array(1, 2, 3) must not be empty
== Working with "containers" ==
You can check whether a collection contains a particular element like this:
traversable must contain ("five")
The contain
syntax shown above can be used with any type C
that has a "containing" nature, evidenced by
an implicit org.scalatest.enablers.Containing[L]
, where L
is left-hand type on
which must
is invoked. In the Containing
companion object, implicits are provided for types GenTraversable[E]
, java.util.Collection[E]
,
java.util.Map[K, V]
, String
, Array[E]
, and Option[E]
.
Here are some examples:
scala> import org.scalatest.matchers.must.Matchers._ import org.scalatest.matchers.must.Matchers._ scala> List(1, 2, 3) must contain (2) scala> Map('a' -> 1, 'b' -> 2, 'c' -> 3) must contain ('b' -> 2) scala> Set(1, 2, 3) must contain (2) scala> Array(1, 2, 3) must contain (2) scala> "123" must contain ('2') scala> Some(2) must contain (2)
ScalaTest's implicit methods that provide the Containing[L]
type classes require an Equality[E]
, where
E
is an element type. For example, to obtain a Containing[Array[Int]]
you must supply an Equality[Int]
,
either implicitly or explicitly. The contain
syntax uses this Equality[E]
to determine containership.
Thus if you want to change how containership is determined for an element type E
, place an implicit Equality[E]
in scope or use the explicitly DSL. Although the implicit parameter required for the contain
syntax is of type Containing[L]
,
implicit conversions are provided in the Containing
companion object from Equality[E]
to the various
types of containers of E
. Here's an example:
scala> import org.scalatest.matchers.must.Matchers._ import org.scalatest.matchers.must.Matchers._ scala> List("Hi", "Di", "Ho") must contain ("ho") org.scalatest.exceptions.TestFailedException: List(Hi, Di, Ho) did not contain element "ho" at ... scala> import org.scalactic.Explicitly._ import org.scalactic.Explicitly._ scala> import org.scalactic.StringNormalizations._ import org.scalactic.StringNormalizations._ scala> (List("Hi", "Di", "Ho") must contain ("ho")) (after being lowerCased)
Note that when you use the explicitly DSL with contain
you need to wrap the entire
contain
expression in parentheses, as shown here.
(List("Hi", "Di", "Ho") must contain ("ho")) (after being lowerCased) ^ ^
In addition to determining whether an object contains another object, you can use contain
to
make other determinations.
For example, the contain
oneOf
syntax ensures that one and only one of the specified elements are
contained in the containing object:
List(1, 2, 3, 4, 5) must contain oneOf (5, 7, 9) Some(7) must contain oneOf (5, 7, 9) "howdy" must contain oneOf ('a', 'b', 'c', 'd')
Note that if multiple specified elements appear in the containing object, oneOf
will fail:
scala> List(1, 2, 3) must contain oneOf (2, 3, 4) org.scalatest.exceptions.TestFailedException: List(1, 2, 3) did not contain one (and only one) of (2, 3, 4) at ...
If you really want to ensure one or more of the specified elements are contained in the containing object,
use atLeastOneOf
, described below, instead of oneOf
. Keep in mind, oneOf
means "exactly one of."
Note also that with any contain
syntax, you can place custom implicit Equality[E]
instances in scope
to customize how containership is determined, or use the explicitly DSL. Here's an example:
(Array("Doe", "Ray", "Me") must contain oneOf ("X", "RAY", "BEAM")) (after being lowerCased)
If you have a collection of elements that you'd like to use in a "one of" comparison, you can use "oneElementOf," like this:
List(1, 2, 3, 4, 5) must contain oneElementOf List(5, 7, 9) Some(7) must contain oneElementOf Vector(5, 7, 9) "howdy" must contain oneElementOf Set('a', 'b', 'c', 'd') (Array("Doe", "Ray", "Me") must contain oneElementOf List("X", "RAY", "BEAM")) (after being lowerCased)
The contain
noneOf
syntax does the opposite of oneOf
: it ensures none of the specified elements
are contained in the containing object:
List(1, 2, 3, 4, 5) must contain noneOf (7, 8, 9) Some(0) must contain noneOf (7, 8, 9) "12345" must contain noneOf ('7', '8', '9')
If you have a collection of elements that you'd like to use in a "none of" comparison, you can use "noElementsOf," like this:
List(1, 2, 3, 4, 5) must contain noElementsOf List(7, 8, 9) Some(0) must contain noElementsOf Vector(7, 8, 9) "12345" must contain noElementsOf Set('7', '8', '9')
== Working with "aggregations" ==
As mentioned, the "contain
," "contain
oneOf
," and "contain
noneOf
" syntax requires a
Containing[L]
be provided, where L
is the left-hand type. Other contain
syntax, which
will be described in this section, requires an Aggregating[L]
be provided, where again L
is the left-hand type.
(An Aggregating[L]
instance defines the "aggregating nature" of a type L
.)
The reason, essentially, is that contain
syntax that makes sense for Option
is enabled by
Containing[L]
, whereas syntax that does not make sense for Option
is enabled
by Aggregating[L]
. For example, it doesn't make sense to assert that an Option[Int]
contains all of a set of integers, as it
could only ever contain one of them. But this does make sense for a type such as List[Int]
that can aggregate zero to many integers.
The Aggregating
companion object provides implicit instances of Aggregating[L]
for types GenTraversable[E]
, java.util.Collection[E]
,
java.util.Map[K, V]
, String
, Array[E]
. Note that these are the same types as are supported with
Containing
, but with Option[E]
missing.
Here are some examples:
The contain
atLeastOneOf
syntax, for example, works for any type L
for which an Aggregating[L]
exists. It ensures
that at least one of (i.e., one or more of) the specified objects are contained in the containing object:
List(1, 2, 3) must contain atLeastOneOf (2, 3, 4) Array(1, 2, 3) must contain atLeastOneOf (3, 4, 5) "abc" must contain atLeastOneOf ('c', 'a', 't')
Similar to Containing[L]
, the implicit methods that provide the Aggregating[L]
instances require an Equality[E]
, where
E
is an element type. For example, to obtain a Aggregating[Vector[String]]
you must supply an Equality[String]
,
either implicitly or explicitly. The contain
syntax uses this Equality[E]
to determine containership.
Thus if you want to change how containership is determined for an element type E
, place an implicit Equality[E]
in scope or use the explicitly DSL. Although the implicit parameter required for the contain
syntax is of type Aggregating[L]
,
implicit conversions are provided in the Aggregating
companion object from Equality[E]
to the various
types of aggregations of E
. Here's an example:
(Vector(" A", "B ") must contain atLeastOneOf ("a ", "b", "c")) (after being lowerCased and trimmed)
If you have a collection of elements that you'd like to use in an "at least one of" comparison, you can use "atLeastOneElementOf," like this:
List(1, 2, 3) must contain atLeastOneElementOf List(2, 3, 4) Array(1, 2, 3) must contain atLeastOneElementOf Vector(3, 4, 5) "abc" must contain atLeastOneElementOf Set('c', 'a', 't') (Vector(" A", "B ") must contain atLeastOneElementOf List("a ", "b", "c")) (after being lowerCased and trimmed)
The "contain
atMostOneOf
" syntax lets you specify a set of objects at most one of which must be contained in the containing object:
List(1, 2, 3, 4, 5) must contain atMostOneOf (5, 6, 7)
If you have a collection of elements that you'd like to use in a "at most one of" comparison, you can use "atMostOneElementOf," like this:
List(1, 2, 3, 4, 5) must contain atMostOneElementOf Vector(5, 6, 7)
The "contain
allOf
" syntax lets you specify a set of objects that must all be contained in the containing object:
List(1, 2, 3, 4, 5) must contain allOf (2, 3, 5)
If you have a collection of elements that you'd like to use in a "all of" comparison, you can use "allElementsOf," like this:
List(1, 2, 3, 4, 5) must contain allElementsOf Array(2, 3, 5)
The "contain
only
" syntax lets you assert that the containing object contains only the specified objects, though it may
contain more than one of each:
List(1, 2, 3, 2, 1) must contain only (1, 2, 3)
The "contain
theSameElementsAs
" and "contain
theSameElementsInOrderAs
syntax differ from the others
in that the right hand side is a GenTraversable[_]
rather than a varargs of Any
. (Note: in a future 2.0 milestone release, possibly
2.0.M6, these will likely be widened to accept any type R
for which an Aggregating[R]
exists.)
The "contain
theSameElementsAs
" syntax lets you assert that two aggregations contain the same objects:
List(1, 2, 2, 3, 3, 3) must contain theSameElementsAs Vector(3, 2, 3, 1, 2, 3)
The number of times any family of equal objects appears must also be the same in both the left and right aggregations. The specified objects may appear multiple times, but must appear in the order they appear in the right-hand list. For example, if the last 3 element is left out of the right-hand list in the previous example, the expression would fail because the left side has three 3's and the right hand side has only two:
List(1, 2, 2, 3, 3, 3) must contain theSameElementsAs Vector(3, 2, 3, 1, 2) org.scalatest.exceptions.TestFailedException: List(1, 2, 2, 3, 3, 3) did not contain the same elements as Vector(3, 2, 3, 1, 2) at ...
Note that no onlyElementsOf
matcher is provided, because it would have the same
behavior as theSameElementsAs
. (I.e., if you were looking for onlyElementsOf
, please use theSameElementsAs
instead.)
== Working with "sequences" ==
The rest of the contain
syntax, which
will be described in this section, requires a Sequencing[L]
be provided, where again L
is the left-hand type.
(A Sequencing[L]
instance defines the "sequencing nature" of a type L
.)
The reason, essentially, is that contain
syntax that implies an "order" of elements makes sense only for types that place elements in a sequence.
For example, it doesn't make sense to assert that a Map[String, Int]
or Set[Int]
contains all of a set of integers in a particular
order, as these types don't necessarily define an order for their elements. But this does make sense for a type such as Seq[Int]
that does define
an order for its elements.
The Sequencing
companion object provides implicit instances of Sequencing[L]
for types GenSeq[E]
, java.util.List[E]
,
String
, and Array[E]
.
Here are some examples:
Similar to Containing[L]
, the implicit methods that provide the Aggregating[L]
instances require an Equality[E]
, where
E
is an element type. For example, to obtain a Aggregating[Vector[String]]
you must supply an Equality[String]
,
either implicitly or explicitly. The contain
syntax uses this Equality[E]
to determine containership.
Thus if you want to change how containership is determined for an element type E
, place an implicit Equality[E]
in scope or use the explicitly DSL. Although the implicit parameter required for the contain
syntax is of type Aggregating[L]
,
implicit conversions are provided in the Aggregating
companion object from Equality[E]
to the various
types of aggregations of E
. Here's an example:
The "contain
inOrderOnly
" syntax lets you assert that the containing object contains only the specified objects, in order.
The specified objects may appear multiple times, but must appear in the order they appear in the right-hand list. Here's an example:
List(1, 2, 2, 3, 3, 3) must contain inOrderOnly (1, 2, 3)
The "contain
inOrder
" syntax lets you assert that the containing object contains only the specified objects in order, like
inOrderOnly
, but allows other objects to appear in the left-hand aggregation as well:
contain more than one of each:
List(0, 1, 2, 2, 99, 3, 3, 3, 5) must contain inOrder (1, 2, 3)
If you have a collection of elements that you'd like to use in a "in order" comparison, you can use "inOrderElementsOf," like this:
List(0, 1, 2, 2, 99, 3, 3, 3, 5) must contain inOrderElementsOf Array(1, 2, 3)
Note that "order" in inOrder
, inOrderOnly
, and theSameElementsInOrderAs
(described below)
in the Aggregation[L]
instances built-in to ScalaTest is defined as "iteration order".
Lastly, the "contain
theSameElementsInOrderAs
" syntax lets you assert that two aggregations contain
the same exact elements in the same (iteration) order:
List(1, 2, 3) must contain theSameElementsInOrderAs collection.mutable.TreeSet(3, 2, 1)
The previous assertion succeeds because the iteration order of aTreeSet
is the natural
ordering of its elements, which in this case is 1, 2, 3. An iterator obtained from the left-hand List
will produce the same elements
in the same order.
Note that no inOrderOnlyElementsOf
matcher is provided, because it would have the same
behavior as theSameElementsInOrderAs
. (I.e., if you were looking for inOrderOnlyElementsOf
, please use theSameElementsInOrderAs
instead.)
== Working with "sortables" ==
You can also ask whether the elements of "sortable" objects (such as Array
s, Java List
s, and GenSeq
s)
are in sorted order, like this:
List(1, 2, 3) mustBe sorted
== Working with iterators ==
Although it seems desireable to provide similar matcher syntax for Scala and Java iterators to that provided for sequences like
Seq
s, Array
, and java.util.List
, the
ephemeral nature of iterators makes this problematic. Some syntax (such as must
contain
) is relatively straightforward to
support on iterators, but other syntax (such
as, for example, Inspector
expressions on nested iterators) is not. Rather
than allowing inconsistencies between sequences and iterators in the API, we chose to not support any such syntax directly on iterators:
scala> val it = List(1, 2, 3).iterator it: Iterator[Int] = non-empty iterator scala> it must contain (2) <console>:15: error: could not find implicit value for parameter typeClass1: org.scalatest.enablers.Containing[Iterator[Int]] it must contain (2) ^
Instead, you will need to convert your iterators to a sequence explicitly before using them in matcher expressions:
scala> it.toStream must contain (2)
We recommend you convert (Scala or Java) iterators to Stream
s, as shown in the previous example, so that you can
continue to reap any potential benefits provided by the laziness of the underlying iterator.
== Inspector shorthands ==
You can use the Inspectors
syntax with matchers as well as assertions. If you have a multi-dimensional collection, such as a
list of lists, using Inspectors
is your best option:
val yss = List( List(1, 2, 3), List(1, 2, 3), List(1, 2, 3) ) forAll (yss) { ys => forAll (ys) { y => y must be > 0 } }
For assertions on one-dimensional collections, however, matchers provides "inspector shorthands." Instead of writing:
val xs = List(1, 2, 3) forAll (xs) { x => x must be < 10 }
You can write:
all (xs) must be < 10
The previous statement asserts that all elements of the xs
list must be less than 10.
All of the inspectors have shorthands in matchers. Here is the full list:
-
all
- succeeds if the assertion holds true for every element -
atLeast
- succeeds if the assertion holds true for at least the specified number of elements -
atMost
- succeeds if the assertion holds true for at most the specified number of elements -
between
- succeeds if the assertion holds true for between the specified minimum and maximum number of elements, inclusive -
every
- same asall
, but lists all failing elements if it fails (whereasall
just reports the first failing element) -
exactly
- succeeds if the assertion holds true for exactly the specified number of elements
Here are some examples:
scala> import org.scalatest.matchers.must.Matchers._ import org.scalatest.matchers.must.Matchers._ scala> val xs = List(1, 2, 3, 4, 5) xs: List[Int] = List(1, 2, 3, 4, 5) scala> all (xs) must be > 0 scala> atMost (2, xs) must be >= 4 scala> atLeast (3, xs) must be < 5 scala> between (2, 3, xs) must (be > 1 and be < 5) scala> exactly (2, xs) must be <= 2 scala> every (xs) must be < 10 scala> // And one that fails... scala> exactly (2, xs) mustEqual 2 org.scalatest.exceptions.TestFailedException: 'exactly(2)' inspection failed, because only 1 element satisfied the assertion block at index 1: at index 0, 1 did not equal 2, at index 2, 3 did not equal 2, at index 3, 4 did not equal 2, at index 4, 5 did not equal 2 in List(1, 2, 3, 4, 5) at ...
Like Inspectors
, objects used with inspector shorthands can be any type T
for which a Collecting[T, E]
is availabe, which by default includes GenTraversable
,
Java Collection
, Java Map
, Array
s, and String
s.
Here are some examples:
scala> import org.scalatest._ import org.scalatest._ scala> import matchers.must.Matchers._ import matchers.must.Matchers._ scala> all (Array(1, 2, 3)) must be < 5 scala> import collection.JavaConverters._ import collection.JavaConverters._ scala> val js = List(1, 2, 3).asJava js: java.util.List[Int] = [1, 2, 3] scala> all (js) must be < 5 scala> val jmap = Map("a" -> 1, "b" -> 2).asJava jmap: java.util.Map[String,Int] = {a=1, b=2} scala> atLeast(1, jmap) mustBe Entry("b", 2) scala> atLeast(2, "hello, world!") mustBe 'o'
== Single-element collections ==
To assert both that a collection contains just one "lone" element as well as something else about that element, you can use
the loneElement
syntax provided by trait LoneElement
. For example, if a
Set[Int]
must contain just one element, an Int
less than or equal to 10, you could write:
import LoneElement._ set.loneElement must be <= 10
You can invoke loneElement
on any type T
for which an implicit Collecting[E, T]
is available, where E
is the element type returned by the loneElement
invocation. By default, you can use loneElement
on GenTraversable
, Java Collection
, Java Map
, Array
, and String
.
== Java collections and maps ==
You can use similar syntax on Java collections (java.util.Collection
) and maps (java.util.Map
).
For example, you can check whether a Java Collection
or Map
is empty
,
like this:
javaCollection must be ('empty) javaMap must be ('empty)
Even though Java's List
type doesn't actually have a length
or getLength
method,
you can nevertheless check the length of a Java List
(java.util.List
) like this:
javaList must have length 9
You can check the size of any Java Collection
or Map
, like this:
javaMap must have size 20 javaSet must have size 90
In addition, you can check whether a Java Collection
contains a particular
element, like this:
javaCollection must contain ("five")
One difference to note between the syntax supported on Java and Scala collections is that
in Java, Map
is not a subtype of Collection
, and does not
actually define an element type. You can ask a Java Map
for an "entry set"
via the entrySet
method, which will return the Map
's key/value pairs
wrapped in a set of java.util.Map.Entry
, but a Map
is not actually
a collection of Entry
. To make Java Map
s easier to work with, however,
ScalaTest matchers allows you to treat a Java Map
as a collection of Entry
,
and defines a convenience implementation of java.util.Map.Entry
in
org.scalatest.Entry
. Here's how you use it:
javaMap must contain (Entry(2, 3)) javaMap must contain oneOf (Entry(2, 3), Entry(3, 4))
You can you alse just check whether a Java Map
contains a particular key, or value, like this:
javaMap must contain key 1 javaMap must contain value "Howdy"
== String
s and Array
s as collections ==
You can also use all the syntax described above for Scala and Java collections on Array
s and
String
s. Here are some examples:
scala> import org.scalatest._ import org.scalatest._ scala> import matchers.must.Matchers._ import matchers.must.Matchers._ scala> atLeast (2, Array(1, 2, 3)) must be > 1 scala> atMost (2, "halloo") mustBe 'o' scala> Array(1, 2, 3) mustBe sorted scala> "abcdefg" mustBe sorted scala> Array(1, 2, 3) must contain atMostOneOf (3, 4, 5) scala> "abc" must contain atMostOneOf ('c', 'd', 'e')
== be
as an equality comparison ==
All uses of be
other than those shown previously perform an equality comparison. They work
the same as equal
when it is used with default equality. This redundancy between be
and equals
exists in part
because it enables syntax that sometimes sounds more natural. For example, instead of writing:
result must equal (null)
You can write:
result must be (null)
(Hopefully you won't write that too much given null
is error prone, and Option
is usually a better, well, option.)
As mentioned previously, the other difference between equal
and be
is that equal
delegates the equality check to an Equality
typeclass, whereas
be
always uses default equality.
Here are some other examples of be
used for equality comparison:
sum must be (7.0) boring must be (false) fun must be (true) list must be (Nil) option must be (None) option must be (Some(1))
As with equal
used with default equality, using be
on arrays results in deep
being called on both arrays prior to
calling equal
. As a result,
the following expression would not throw a TestFailedException
:
Array(1, 2) must be (Array(1, 2)) // succeeds (i.e., does not throw TestFailedException)
Because be
is used in several ways in ScalaTest matcher syntax, just as it is used in many ways in English, one
potential point of confusion in the event of a failure is determining whether be
was being used as an equality comparison or
in some other way, such as a property assertion. To make it more obvious when be
is being used for equality, the failure
messages generated for those equality checks will include the word equal
in them. For example, if this expression fails with a
TestFailedException
:
option must be (Some(1))
The detail message in that TestFailedException
will include the words "equal to"
to signify be
was in this case being used for equality comparison:
Some(2) was not equal to Some(1)
== Being negative ==
If you wish to check the opposite of some condition, you can simply insert not
in the expression.
Here are a few examples:
result must not be (null) sum must not be <= (10) mylist must not equal (yourList) string must not startWith ("Hello")
== Checking that a snippet of code does not compile ==
Often when creating libraries you may wish to ensure that certain arrangements of code that
represent potential “user errors” do not compile, so that your library is more error resistant.
ScalaTest Matchers
trait includes the following syntax for that purpose:
"val a: String = 1" mustNot compile
If you want to ensure that a snippet of code does not compile because of a type error (as opposed to a syntax error), use:
"val a: String = 1" mustNot typeCheck
Note that the mustNot
typeCheck
syntax will only succeed if the given snippet of code does not
compile because of a type error. A syntax error will still result on a thrown TestFailedException
.
If you want to state that a snippet of code does compile, you can make that more obvious with:
"val a: Int = 1" must compile
Although the previous three constructs are implemented with macros that determine at compile time whether the snippet of code represented by the string does or does not compile, errors are reported as test failures at runtime.
== Logical expressions with and
and or
==
You can also combine matcher expressions with and
and/or or
, however,
you must place parentheses or curly braces around the and
or or
expression. For example,
this and
-expression would not compile, because the parentheses are missing:
map must contain key ("two") and not contain value (7) // ERROR, parentheses missing!
Instead, you need to write:
map must (contain key ("two") and not contain value (7))
Here are some more examples:
number must (be > (0) and be <= (10)) option must (equal (Some(List(1, 2, 3))) or be (None)) string must ( equal ("fee") or equal ("fie") or equal ("foe") or equal ("fum") )
Two differences exist between expressions composed of these and
and or
operators and the expressions you can write
on regular Boolean
s using its &&
and ||
operators. First, expressions with and
and or
do not short-circuit. The following contrived expression, for example, would print "hello, world!"
:
"yellow" must (equal ("blue") and equal { println("hello, world!"); "green" })
In other words, the entire and
or or
expression is always evaluated, so you'll see any side effects
of the right-hand side even if evaluating
only the left-hand side is enough to determine the ultimate result of the larger expression. Failure messages produced by these
expressions will "short-circuit," however,
mentioning only the left-hand side if that's enough to determine the result of the entire expression. This "short-circuiting" behavior
of failure messages is intended
to make it easier and quicker for you to ascertain which part of the expression caused the failure. The failure message for the previous
expression, for example, would be:
"yellow" did not equal "blue"
Most likely this lack of short-circuiting would rarely be noticeable, because evaluating the right hand side will usually not
involve a side effect. One situation where it might show up, however, is if you attempt to and
a null
check on a variable with an expression
that uses the variable, like this:
map must (not be (null) and contain key ("ouch"))
If map
is null
, the test will indeed fail, but with a NullArgumentException
, not a
TestFailedException
. Here, the NullArgumentException
is the visible right-hand side effect. To get a
TestFailedException
, you would need to check each assertion separately:
map must not be (null) map must contain key ("ouch")
If map
is null
in this case, the null
check in the first expression will fail with
a TestFailedException
, and the second expression will never be executed.
The other difference with Boolean
operators is that although &&
has a higher precedence than ||
,
and
and or
have the same precedence. Thus although the Boolean
expression (a || b && c)
will evaluate the &&
expression
before the ||
expression, like (a || (b && c))
, the following expression:
traversable must (contain (7) or contain (8) and have size (9))
Will evaluate left to right, as:
traversable must ((contain (7) or contain (8)) and have size (9))
If you really want the and
part to be evaluated first, you'll need to put in parentheses, like this:
traversable must (contain (7) or (contain (8) and have size (9)))
== Working with Option
s ==
You can work with options using ScalaTest's equality, empty
,
defined
, and contain
syntax.
For example, if you wish to check whether an option is None
, you can write any of:
option mustEqual None option mustBe None option must === (None) option mustBe empty
If you wish to check an option is defined, and holds a specific value, you can write any of:
option mustEqual Some("hi") option mustBe Some("hi") option must === (Some("hi"))
If you only wish to check that an option is defined, but don't care what it's value is, you can write:
option mustBe defined
If you mix in (or import the members of) OptionValues
,
you can write one statement that indicates you believe an option must be defined and then say something else about its value. Here's an example:
import org.scalatest.OptionValues._ option.value must be < 7
As mentioned previously, you can use also use ScalaTest's contain
, contain oneOf
, and
contain noneOf
syntax with options:
Some(2) must contain (2) Some(7) must contain oneOf (5, 7, 9) Some(0) must contain noneOf (7, 8, 9)
== Checking arbitrary properties with have
==
Using have
, you can check properties of any type, where a property is an attribute of any
object that can be retrieved either by a public field, method, or JavaBean-style get
or is
method, like this:
book must have ( 'title ("Programming in Scala"), 'author (List("Odersky", "Spoon", "Venners")), 'pubYear (2008) )
This expression will use reflection to ensure the title
, author
, and pubYear
properties of object book
are equal to the specified values. For example, it will ensure that book
has either a public Java field or method
named title
, or a public method named getTitle
, that when invoked (or accessed in the field case) results
in a the string "Programming in Scala"
. If all specified properties exist and have their expected values, respectively,
execution will continue. If one or more of the properties either does not exist, or exists but results in an unexpected value,
a TestFailedException
will be thrown that explains the problem. (For the details on how a field or method is selected during this
process, see the documentation for HavePropertyMatcherGenerator
.)
When you use this syntax, you must place one or more property values in parentheses after have
, seperated by commas, where a property
value is a symbol indicating the name of the property followed by the expected value in parentheses. The only exceptions to this rule is the syntax
for checking size and length shown previously, which does not require parentheses. If you forget and put parentheses in, however, everything will
still work as you'd expect. Thus instead of writing:
array must have length (3) set must have size (90)
You can alternatively, write:
array must have (length (3)) set must have (size (90))
If a property has a value different from the specified expected value, a TestFailedError
will be thrown
with a detailed message that explains the problem. For example, if you assert the following on
a book
whose title is Moby Dick
:
book must have ('title ("A Tale of Two Cities"))
You'll get a TestFailedException
with this detail message:
The title property had value "Moby Dick", instead of its expected value "A Tale of Two Cities", on object Book("Moby Dick", "Melville", 1851)
If you prefer to check properties in a type-safe manner, you can use a HavePropertyMatcher
.
This would allow you to write expressions such as:
book must have ( title ("Programming in Scala"), author (List("Odersky", "Spoon", "Venners")), pubYear (2008) )
These expressions would fail to compile if must
is used on an inappropriate type, as determined
by the type parameter of the HavePropertyMatcher
being used. (For example, title
in this example
might be of type HavePropertyMatcher[org.publiclibrary.Book]
. If used with an appropriate type, such an expression will compile
and at run time the property method or field will be accessed directly; i.e., no reflection will be used.
See the documentation for HavePropertyMatcher
for more information.
== Using length
and size
with HavePropertyMatcher
s ==
If you want to use length
or size
syntax with your own custom HavePropertyMatcher
s, you
can do so, but you must write (of [“the type”])
afterwords. For example, you could write:
book must have ( title ("A Tale of Two Cities"), length (220) (of [Book]), author ("Dickens") )
Prior to ScalaTest 2.0, “length
(22)
” yielded a HavePropertyMatcher[Any, Int]
that used reflection to dynamically look
for a length
field or getLength
method. In ScalaTest 2.0, “length
(22)
” yields a
MatcherFactory1[Any, Length]
, so it is no longer a HavePropertyMatcher
. The (of [<type>])
syntax converts the
the MatcherFactory1[Any, Length]
to a HavePropertyMatcher[<type>, Int]
.
== Checking that an expression matches a pattern ==
ScalaTest's Inside
trait allows you to make assertions after a pattern match.
Here's an example:
case class Name(first: String, middle: String, last: String) val name = Name("Jane", "Q", "Programmer") inside(name) { case Name(first, _, _) => first must startWith ("S") }
You can use inside
to just ensure a pattern is matched, without making any further assertions, but a better
alternative for that kind of assertion is matchPattern
. The matchPattern
syntax allows you
to express that you expect a value to match a particular pattern, no more and no less:
name must matchPattern { case Name("Sarah", _, _) => }
== Using custom matchers ==
If none of the built-in matcher syntax (or options shown so far for extending the syntax) satisfy a particular need you have, you can create
custom Matcher
s that allow
you to place your own syntax directly after must
. For example, class java.io.File
has a method isHidden
, which
indicates whether a file of a certain path and name is hidden. Because the isHidden
method takes no parameters and returns Boolean
,
you can call it using be
with a symbol or BePropertyMatcher
, yielding assertions like:
file must be ('hidden) // using a symbol file must be (hidden) // using a BePropertyMatcher
If it doesn't make sense to have your custom syntax follow be
, you might want to create a custom Matcher
instead, so your syntax can follow must
directly. For example, you might want to be able to check whether
a java.io.File
's name ends with a particular extension, like this:
// using a plain-old Matcher file must endWithExtension ("txt")
ScalaTest provides several mechanism to make it easy to create custom matchers, including ways to compose new matchers
out of existing ones complete with new error messages. For more information about how to create custom
Matcher
s, please see the documentation for the Matcher
trait.
== Checking for expected exceptions ==
Sometimes you need to test whether a method throws an expected exception under certain circumstances, such
as when invalid arguments are passed to the method. With Matchers
mixed in, you can
check for an expected exception like this:
an [IndexOutOfBoundsException] must be thrownBy s.charAt(-1)
If charAt
throws an instance of StringIndexOutOfBoundsException
,
this expression will result in that exception. But if charAt
completes normally, or throws a different
exception, this expression will complete abruptly with a TestFailedException
.
If you need to further isnpect an expected exception, you can capture it using this syntax:
val thrown = the [IndexOutOfBoundsException] thrownBy s.charAt(-1)
This expression returns the caught exception so that you can inspect it further if you wish, for example, to ensure that data contained inside the exception has the expected values. Here's an example:
thrown.getMessage must equal ("String index out of range: -1")
If you prefer you can also capture and inspect an expected exception in one statement, like this:
the [ArithmeticException] thrownBy 1 / 0 must have message "/ by zero" the [IndexOutOfBoundsException] thrownBy { s.charAt(-1) } must have message "String index out of range: -1"
You can also state that no exception must be thrown by some code, like this:
noException must be thrownBy 0 / 1
== Those pesky parens ==
Perhaps the most tricky part of writing assertions using ScalaTest matchers is remembering when you need or don't need parentheses, but bearing in mind a few simple rules should help. It is also reassuring to know that if you ever leave off a set of parentheses when they are required, your code will not compile. Thus the compiler will help you remember when you need the parens. That said, the rules are:
- Although you don't always need them, you may choose to always put parentheses
around right-hand values, such as the
7
innum must equal (7)
:
result must equal (4) array must have length (3) book must have ( 'title ("Programming in Scala"), 'author (List("Odersky", "Spoon", "Venners")), 'pubYear (2008) ) option must be ('defined) catMap must (contain key (9) and contain value ("lives")) keyEvent must be an ('actionKey) javaSet must have size (90)
- Except for
length
,size
andmessage
, you must always put parentheses around the list of one or more property values following ahave
:
file must (exist and have ('name ("temp.txt"))) book must have ( title ("Programming in Scala"), author (List("Odersky", "Spoon", "Venners")), pubYear (2008) ) javaList must have length (9) // parens optional for length and size
- You must always put parentheses around
and
andor
expressions, as in:
catMap must (contain key (9) and contain value ("lives")) number must (equal (2) or equal (4) or equal (8))
- Although you don't always need them, you may choose to always put parentheses
around custom
Matcher
s when they appear directly afternot
:
file must exist file must not (exist) file must (exist and have ('name ("temp.txt"))) file must (not (exist) and have ('name ("temp.txt")) file must (have ('name ("temp.txt") or exist) file must (have ('name ("temp.txt") or not (exist))
That's it. With a bit of practice it should become natural to you, and the compiler will always be there to tell you if you forget a set of needed parentheses.
Note: ScalaTest's matchers are in part inspired by the matchers of RSpec,
Hamcrest, and
specs2, and its “mustNot compile
” syntax
by the illTyped
macro of shapeless.
- Companion:
- object
Type members
Classlikes
This class is part of the ScalaTest matchers DSL. Please see the documentation for Matchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for Matchers
for an overview of
the matchers DSL.
This class is used in conjunction with an implicit conversion to enable must
methods to
be invoked on objects of type Any
.
This class is part of the ScalaTest matchers DSL. Please see the documentation for Matchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for Matchers
for an overview of
the matchers DSL.
This class is used as the result of an implicit conversion from class Symbol
, to enable symbols to be
used in have ('author ("Dickens"))
syntax. The name of the implicit conversion method is
convertSymbolToHavePropertyMatcherGenerator
.
Class HavePropertyMatcherGenerator
's primary constructor takes a Symbol
. The
apply
method uses reflection to find and access a property that has the name specified by the
Symbol
passed to the constructor, so it can determine if the property has the expected value
passed to apply
.
If the symbol passed is 'title
, for example, the apply
method
will use reflection to look for a public Java field named
"title", a public method named "title", or a public method named "getTitle".
If a method, it must take no parameters. If multiple candidates are found,
the apply
method will select based on the following algorithm:
Field | Method | "get" Method | Result |
---|---|---|---|
Throws TestFailedException , because no candidates found | |||
getTitle() | Invokes getTitle() | ||
title() | Invokes title() | ||
title() | getTitle() | Invokes title() (this can occur when BeanProperty annotation is used) | |
title | Accesses field title | ||
title | getTitle() | Invokes getTitle() | |
title | title() | Invokes title() | |
title | title() | getTitle() | Invokes title() (this can occur when BeanProperty annotation is used) |
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
This class is part of the ScalaTest matchers DSL. Please see the documentation for InspectorsMatchers
for an overview of
the matchers DSL.
Inherited classlikes
Class used via an implicit conversion to enable two objects to be compared with
===
and !==
with a Boolean
result and an enforced type constraint between
two object types. For example:
Class used via an implicit conversion to enable two objects to be compared with
===
and !==
with a Boolean
result and an enforced type constraint between
two object types. For example:
assert(a === b) assert(c !== d)
You can also check numeric values against another with a tolerance. Here are some examples:
assert(a === (2.0 +- 0.1)) assert(c !== (2.0 +- 0.1))
- Value parameters:
- leftSide
An object to convert to
Equalizer
, which represents the value on the left side of a===
or!==
invocation.
- Inherited from:
- TripleEqualsSupport
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
Instances of this class are returned via the decided
by
<an Equality>
syntax, and enables afterBeing
to be invoked on it. Here's an example, given an
Equality[String]
named myStringEquality
:
result should equal ("hello") (decided by myStringEquality afterBeing lowerCased)
- Inherited from:
- Explicitly
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
- Inherited from:
- Explicitly
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
Instances of this class are returned via the decided
by
<an Equivalence>
syntax, and enables afterBeing
to be invoked on it. Here's an example, given an
Equivalence[String]
named myStringEquivalence
:
result should equal ("hello") (determined by myStringEquivalence afterBeing lowerCased)
- Inherited from:
- Explicitly
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
- Inherited from:
- Explicitly
Class used via an implicit conversion to enable any two objects to be compared with
===
and !==
with a Boolean
result and no enforced type constraint between
two object types. For example:
Class used via an implicit conversion to enable any two objects to be compared with
===
and !==
with a Boolean
result and no enforced type constraint between
two object types. For example:
assert(a === b) assert(c !== d)
You can also check numeric values against another with a tolerance. Here are some examples:
assert(a === (2.0 +- 0.1)) assert(c !== (2.0 +- 0.1))
- Value parameters:
- leftSide
An object to convert to
Equalizer
, which represents the value on the left side of a===
or!==
invocation.
- Inherited from:
- TripleEqualsSupport
Wrapper class with a +-
method that, given a Numeric
argument, returns a Spread
.
Wrapper class with a +-
method that, given a Numeric
argument, returns a Spread
.
- Value parameters:
- tolerance
the tolerance with which to create (and return) a
Spread
- Inherited from:
- Tolerance
This class supports the syntax of FlatSpec
, WordSpec
, fixture.FlatSpec
,
and fixture.WordSpec
.
This class supports the syntax of FlatSpec
, WordSpec
, fixture.FlatSpec
,
and fixture.WordSpec
.
This class is used in conjunction with an implicit conversion to enable must
methods to
be invoked on String
s.
- Inherited from:
- MustVerb
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
This class is part of the Scalactic “explicitly DSL”. Please
see the documentation for Explicitly
for an overview of
the explicitly DSL.
- Inherited from:
- Explicitly
Value members
Concrete methods
This method enables the following syntax:
This method enables the following syntax:
num must (not be < (10) and not be > (17)) ^
This method enables the following syntax:
This method enables the following syntax:
num must (not be <= (10) and not be > (17)) ^
This method enables the following syntax:
This method enables the following syntax:
num must (not be > (10) and not be < (7)) ^
This method enables the following syntax:
This method enables the following syntax:
num must (not be >= (10) and not be < (7)) ^
This method enables the following syntax:
This method enables the following syntax:
a [RuntimeException] must be thrownBy { ... } ^
This method enables the following syntax:
This method enables the following syntax:
all(xs) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for scala.collection.GenMap
:
This method enables the following syntax for scala.collection.GenMap
:
all(map) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for java.util.Map
:
This method enables the following syntax for java.util.Map
:
all(jmap) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for String
:
This method enables the following syntax for String
:
all(str) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (allElementsOf(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (allOf(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
an [Exception] must be thrownBy { ... } ^
This method enables the following syntax:
This method enables the following syntax:
atLeast(1, xs) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for scala.collection.GenMap
:
This method enables the following syntax for scala.collection.GenMap
:
atLeast(1, map) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for java.util.Map
:
This method enables the following syntax for java.util.Map
:
atLeast(1, jmap) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for String
:
This method enables the following syntax for String
:
atLeast(1, str) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (atLeastOneElementOf (List(1, 2))) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (atLeastOneOf(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
atMost(3, xs) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for scala.collection.GenMap
:
This method enables the following syntax for scala.collection.GenMap
:
atMost(3, map) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for java.util.Map
:
This method enables the following syntax for java.util.Map
:
atMost(3, jmap) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for String
:
This method enables the following syntax for String
:
atMost(3, str) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (atMostOneElementOf (List(1, 2))) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (atMostOneOf(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
between(1, 3, xs) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for java.util.Map
:
This method enables the following syntax for java.util.Map
:
between(1, 3, jmap) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for String
:
This method enables the following syntax for String
:
between(1, 3, str) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax:
This method enables the following syntax:
list must (not be definedAt (7) and not be definedAt (9)) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result must equal (100 +- 1) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result must equal (null) ^
This method enables the following syntax:
This method enables the following syntax:
every(xs) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for scala.collection.GenMap
:
This method enables the following syntax for scala.collection.GenMap
:
every(map) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for java.util.Map
:
This method enables the following syntax for java.util.Map
:
every(jmap) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for String
:
This method enables the following syntax for String
:
every(str) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax:
This method enables the following syntax:
exactly(xs) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for scala.collection.GenMap
:
This method enables the following syntax for scala.collection.GenMap
:
exactly(map) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for java.util.Map
:
This method enables the following syntax for java.util.Map
:
exactly(jmap) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for String
:
This method enables the following syntax for String
:
exactly(str) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (inOrder(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (inOrderElementsOf List(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (inOrderOnly(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
exception must not have message ("file not found") ^
This method enables the following syntax:
This method enables the following syntax:
no(xs) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for java.util.Map
:
This method enables the following syntax for java.util.Map
:
no(jmap) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax for String
:
This method enables the following syntax for String
:
no(str) must fullymatch regex ("Hel*o world".r) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (noElementsOf List(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (noneOf(1, 2)) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
book must have (message ("A TALE OF TWO CITIES") (of [Book]), title ("A Tale of Two Cities")) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (oneElementOf (List(1, 2))) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (oneOf(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (only(1, 2)) ^
This method enables the following syntax:
This method enables the following syntax:
the [FileNotFoundException] must be thrownBy { ... } ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (theSameElementsAs(List(1, 2, 3))) ^
This method enables the following syntax:
This method enables the following syntax:
List(1, 2, 3) must contain (theSameElementsInOrderAs(List(1, 2))) ^
Inherited methods
Returns a TripleEqualsInvocationOnSpread[T]
, given an Spread[T]
, to facilitate
the “<left> should !== (<pivot> +- <tolerance>)
”
syntax of Matchers
.
Returns a TripleEqualsInvocationOnSpread[T]
, given an Spread[T]
, to facilitate
the “<left> should !== (<pivot> +- <tolerance>)
”
syntax of Matchers
.
- Value parameters:
- right
the
Spread[T]
against which to compare the left-hand value
- Returns:
a
TripleEqualsInvocationOnSpread
wrapping the passedSpread[T]
value, withexpectingEqual
set tofalse
.- Inherited from:
- TripleEqualsSupport
Returns a TripleEqualsInvocation[Null]
, given a null
reference, to facilitate
the “<left> should !== null
” syntax
of Matchers
.
Returns a TripleEqualsInvocation[Null]
, given a null
reference, to facilitate
the “<left> should !== null
” syntax
of Matchers
.
- Value parameters:
- right
a null reference
- Returns:
a
TripleEqualsInvocation
wrapping the passednull
value, withexpectingEqual
set tofalse
.- Inherited from:
- TripleEqualsSupport
Returns a TripleEqualsInvocation[T]
, given an object of type T
, to facilitate
the “<left> should !== <right>
” syntax
of Matchers
.
Returns a TripleEqualsInvocation[T]
, given an object of type T
, to facilitate
the “<left> should !== <right>
” syntax
of Matchers
.
- Value parameters:
- right
the right-hand side value for an equality assertion
- Returns:
a
TripleEqualsInvocation
wrapping the passed right value, withexpectingEqual
set tofalse
.- Inherited from:
- TripleEqualsSupport
Returns a TripleEqualsInvocationOnSpread[T]
, given an Spread[T]
, to facilitate
the “<left> should === (<pivot> +- <tolerance>)
”
syntax of Matchers
.
Returns a TripleEqualsInvocationOnSpread[T]
, given an Spread[T]
, to facilitate
the “<left> should === (<pivot> +- <tolerance>)
”
syntax of Matchers
.
- Value parameters:
- right
the
Spread[T]
against which to compare the left-hand value
- Returns:
a
TripleEqualsInvocationOnSpread
wrapping the passedSpread[T]
value, withexpectingEqual
set totrue
.- Inherited from:
- TripleEqualsSupport
Returns a TripleEqualsInvocation[Null]
, given a null
reference, to facilitate
the “<left> should === null
” syntax
of Matchers
.
Returns a TripleEqualsInvocation[Null]
, given a null
reference, to facilitate
the “<left> should === null
” syntax
of Matchers
.
- Value parameters:
- right
a null reference
- Returns:
a
TripleEqualsInvocation
wrapping the passednull
value, withexpectingEqual
set totrue
.- Inherited from:
- TripleEqualsSupport
Returns a TripleEqualsInvocation[T]
, given an object of type T
, to facilitate
the “<left> should === <right>
” syntax
of Matchers
.
Returns a TripleEqualsInvocation[T]
, given an object of type T
, to facilitate
the “<left> should === <right>
” syntax
of Matchers
.
- Value parameters:
- right
the right-hand side value for an equality assertion
- Returns:
a
TripleEqualsInvocation
wrapping the passed right value, withexpectingEqual
set totrue
.- Inherited from:
- TripleEqualsSupport
Assert that a boolean condition, described in String
message
, is true.
If the condition is true
, this method returns normally.
Else, it throws TestFailedException
with a helpful error message
appended with the String
obtained by invoking toString
on the
specified clue
as the exception's detail message.
Assert that a boolean condition, described in String
message
, is true.
If the condition is true
, this method returns normally.
Else, it throws TestFailedException
with a helpful error message
appended with the String
obtained by invoking toString
on the
specified clue
as the exception's detail message.
This method is implemented in terms of a Scala macro that will generate a more helpful error message for expressions of this form:
-
assert(a == b, "a good clue")
-
assert(a != b, "a good clue")
-
assert(a === b, "a good clue")
-
assert(a !== b, "a good clue")
-
assert(a > b, "a good clue")
-
assert(a >= b, "a good clue")
-
assert(a < b, "a good clue")
-
assert(a <= b, "a good clue")
-
assert(a startsWith "prefix", "a good clue")
-
assert(a endsWith "postfix", "a good clue")
-
assert(a contains "something", "a good clue")
-
assert(a eq b, "a good clue")
-
assert(a ne b, "a good clue")
-
assert(a > 0 && b > 5, "a good clue")
-
assert(a > 0 || b > 5, "a good clue")
-
assert(a.isEmpty, "a good clue")
-
assert(!a.isEmpty, "a good clue")
-
assert(a.isInstanceOf[String], "a good clue")
-
assert(a.length == 8, "a good clue")
-
assert(a.size == 8, "a good clue")
-
assert(a.exists(_ == 8), "a good clue")
At this time, any other form of expression will just get a TestFailedException
with message saying the given
expression was false. In the future, we will enhance this macro to give helpful error messages in more situations.
In ScalaTest 2.0, however, this behavior was sufficient to allow the ===
that returns Boolean
to be the default in tests. This makes ===
consistent between tests and production
code.
- Value parameters:
- clue
An objects whose
toString
method returns a message to include in a failure report.- condition
the boolean condition to assert
- Throws:
- NullArgumentException
if
message
isnull
.- TestFailedException
if the condition is
false
.
- Inherited from:
- Assertions
Assert that a boolean condition is true.
If the condition is true
, this method returns normally.
Else, it throws TestFailedException
.
Assert that a boolean condition is true.
If the condition is true
, this method returns normally.
Else, it throws TestFailedException
.
This method is implemented in terms of a Scala macro that will generate a more helpful error message for expressions of this form:
-
assert(a == b)
-
assert(a != b)
-
assert(a === b)
-
assert(a !== b)
-
assert(a > b)
-
assert(a >= b)
-
assert(a < b)
-
assert(a <= b)
-
assert(a startsWith "prefix")
-
assert(a endsWith "postfix")
-
assert(a contains "something")
-
assert(a eq b)
-
assert(a ne b)
-
assert(a > 0 && b > 5)
-
assert(a > 0 || b > 5)
-
assert(a.isEmpty)
-
assert(!a.isEmpty)
-
assert(a.isInstanceOf[String])
-
assert(a.length == 8)
-
assert(a.size == 8)
-
assert(a.exists(_ == 8))
At this time, any other form of expression will get a TestFailedException
with message saying the given
expression was false. In the future, we will enhance this macro to give helpful error messages in more situations.
In ScalaTest 2.0, however, this behavior was sufficient to allow the ===
that returns Boolean
to be the default in tests. This makes ===
consistent between tests and production
code.
- Value parameters:
- condition
the boolean condition to assert
- Throws:
- TestFailedException
if the condition is
false
.
- Inherited from:
- Assertions
Asserts that a given string snippet of code passes both the Scala parser and type checker.
Asserts that a given string snippet of code passes both the Scala parser and type checker.
You can use this to make sure a snippet of code compiles:
assertCompiles("val a: Int = 1")
Although assertCompiles
is implemented with a macro that determines at compile time whether
the snippet of code represented by the passed string compiles, errors (i.e.,
snippets of code that do not compile) are reported as test failures at runtime.
- Value parameters:
- code
the snippet of code that should compile
- Inherited from:
- Assertions
Asserts that a given string snippet of code does not pass either the Scala parser or type checker.
Asserts that a given string snippet of code does not pass either the Scala parser or type checker.
Often when creating libraries you may wish to ensure that certain arrangements of code that
represent potential “user errors” do not compile, so that your library is more error resistant.
ScalaTest's Assertions
trait includes the following syntax for that purpose:
assertDoesNotCompile("val a: String = \"a string")
Although assertDoesNotCompile
is implemented with a macro that determines at compile time whether
the snippet of code represented by the passed string doesn't compile, errors (i.e.,
snippets of code that do compile) are reported as test failures at runtime.
Note that the difference between assertTypeError
and assertDoesNotCompile
is
that assertDoesNotCompile
will succeed if the given code does not compile for any reason,
whereas assertTypeError
will only succeed if the given code does not compile because of
a type error. If the given code does not compile because of a syntax error, for example, assertDoesNotCompile
will return normally but assertTypeError
will throw a TestFailedException
.
- Value parameters:
- code
the snippet of code that should not type check
- Inherited from:
- Assertions
Assert that the value passed as expected
equals the value passed as actual
.
If the actual
value equals the expected
value
(as determined by ==
), assertResult
returns
normally. Else, assertResult
throws a
TestFailedException
whose detail message includes the expected and actual values.
Assert that the value passed as expected
equals the value passed as actual
.
If the actual
value equals the expected
value
(as determined by ==
), assertResult
returns
normally. Else, assertResult
throws a
TestFailedException
whose detail message includes the expected and actual values.
- Value parameters:
- actual
the actual value, which should equal the passed
expected
value- expected
the expected value
- Throws:
- TestFailedException
if the passed
actual
value does not equal the passedexpected
value.
- Inherited from:
- Assertions
Assert that the value passed as expected
equals the value passed as actual
.
If the actual
equals the expected
(as determined by ==
), assertResult
returns
normally. Else, if actual
is not equal to expected
, assertResult
throws a
TestFailedException
whose detail message includes the expected and actual values, as well as the String
obtained by invoking toString
on the passed clue
.
Assert that the value passed as expected
equals the value passed as actual
.
If the actual
equals the expected
(as determined by ==
), assertResult
returns
normally. Else, if actual
is not equal to expected
, assertResult
throws a
TestFailedException
whose detail message includes the expected and actual values, as well as the String
obtained by invoking toString
on the passed clue
.
- Value parameters:
- actual
the actual value, which should equal the passed
expected
value- clue
An object whose
toString
method returns a message to include in a failure report.- expected
the expected value
- Throws:
- TestFailedException
if the passed
actual
value does not equal the passedexpected
value.
- Inherited from:
- Assertions
Ensure that an expected exception is thrown by the passed function value. The thrown exception must be an instance of the
type specified by the type parameter of this method. This method invokes the passed
function. If the function throws an exception that's an instance of the specified type,
this method returns Succeeded
. Else, whether the passed function returns normally
or completes abruptly with a different exception, this method throws TestFailedException
.
Ensure that an expected exception is thrown by the passed function value. The thrown exception must be an instance of the
type specified by the type parameter of this method. This method invokes the passed
function. If the function throws an exception that's an instance of the specified type,
this method returns Succeeded
. Else, whether the passed function returns normally
or completes abruptly with a different exception, this method throws TestFailedException
.
Note that the type specified as this method's type parameter may represent any subtype of
AnyRef
, not just Throwable
or one of its subclasses. In
Scala, exceptions can be caught based on traits they implement, so it may at times make sense
to specify a trait that the intercepted exception's class must mix in. If a class instance is
passed for a type that could not possibly be used to catch an exception (such as String
,
for example), this method will complete abruptly with a TestFailedException
.
Also note that the difference between this method and intercept
is that this method
does not return the expected exception, so it does not let you perform further assertions on
that exception. Instead, this method returns Succeeded
, which means it can
serve as the last statement in an async- or safe-style suite. It also indicates to the reader
of the code that nothing further is expected about the thrown exception other than its type.
The recommended usage is to use assertThrows
by default, intercept
only when you
need to inspect the caught exception further.
- Value parameters:
- classTag
an implicit
ClassTag
representing the type of the specified type parameter.- f
the function value that should throw the expected exception
- Returns:
the
Succeeded
singleton, if an exception of the expected type is thrown- Throws:
- TestFailedException
if the passed function does not complete abruptly with an exception that's an instance of the specified type.
- Inherited from:
- Assertions
Asserts that a given string snippet of code does not pass the Scala type checker, failing if the given snippet does not pass the Scala parser.
Asserts that a given string snippet of code does not pass the Scala type checker, failing if the given snippet does not pass the Scala parser.
Often when creating libraries you may wish to ensure that certain arrangements of code that
represent potential “user errors” do not compile, so that your library is more error resistant.
ScalaTest's Assertions
trait includes the following syntax for that purpose:
assertTypeError("val a: String = 1")
Although assertTypeError
is implemented with a macro that determines at compile time whether
the snippet of code represented by the passed string type checks, errors (i.e.,
snippets of code that do type check) are reported as test failures at runtime.
Note that the difference between assertTypeError
and assertDoesNotCompile
is
that assertDoesNotCompile
will succeed if the given code does not compile for any reason,
whereas assertTypeError
will only succeed if the given code does not compile because of
a type error. If the given code does not compile because of a syntax error, for example, assertDoesNotCompile
will return normally but assertTypeError
will throw a TestFailedException
.
- Value parameters:
- code
the snippet of code that should not type check
- Inherited from:
- Assertions
Assume that a boolean condition, described in String
message
, is true.
If the condition is true
, this method returns normally.
Else, it throws TestCanceledException
with a helpful error message
appended with String
obtained by invoking toString
on the
specified clue
as the exception's detail message.
Assume that a boolean condition, described in String
message
, is true.
If the condition is true
, this method returns normally.
Else, it throws TestCanceledException
with a helpful error message
appended with String
obtained by invoking toString
on the
specified clue
as the exception's detail message.
This method is implemented in terms of a Scala macro that will generate a more helpful error message for expressions of this form:
-
assume(a == b, "a good clue")
-
assume(a != b, "a good clue")
-
assume(a === b, "a good clue")
-
assume(a !== b, "a good clue")
-
assume(a > b, "a good clue")
-
assume(a >= b, "a good clue")
-
assume(a < b, "a good clue")
-
assume(a <= b, "a good clue")
-
assume(a startsWith "prefix", "a good clue")
-
assume(a endsWith "postfix", "a good clue")
-
assume(a contains "something", "a good clue")
-
assume(a eq b, "a good clue")
-
assume(a ne b, "a good clue")
-
assume(a > 0 && b > 5, "a good clue")
-
assume(a > 0 || b > 5, "a good clue")
-
assume(a.isEmpty, "a good clue")
-
assume(!a.isEmpty, "a good clue")
-
assume(a.isInstanceOf[String], "a good clue")
-
assume(a.length == 8, "a good clue")
-
assume(a.size == 8, "a good clue")
-
assume(a.exists(_ == 8), "a good clue")
At this time, any other form of expression will just get a TestCanceledException
with message saying the given
expression was false. In the future, we will enhance this macro to give helpful error messages in more situations.
In ScalaTest 2.0, however, this behavior was sufficient to allow the ===
that returns Boolean
to be the default in tests. This makes ===
consistent between tests and production
code.
- Value parameters:
- clue
An objects whose
toString
method returns a message to include in a failure report.- condition
the boolean condition to assume
- Throws:
- NullArgumentException
if
message
isnull
.- TestCanceledException
if the condition is
false
.
- Inherited from:
- Assertions
Assume that a boolean condition is true.
If the condition is true
, this method returns normally.
Else, it throws TestCanceledException
.
Assume that a boolean condition is true.
If the condition is true
, this method returns normally.
Else, it throws TestCanceledException
.
This method is implemented in terms of a Scala macro that will generate a more helpful error message for expressions of this form:
-
assume(a == b)
-
assume(a != b)
-
assume(a === b)
-
assume(a !== b)
-
assume(a > b)
-
assume(a >= b)
-
assume(a < b)
-
assume(a <= b)
-
assume(a startsWith "prefix")
-
assume(a endsWith "postfix")
-
assume(a contains "something")
-
assume(a eq b)
-
assume(a ne b)
-
assume(a > 0 && b > 5)
-
assume(a > 0 || b > 5)
-
assume(a.isEmpty)
-
assume(!a.isEmpty)
-
assume(a.isInstanceOf[String])
-
assume(a.length == 8)
-
assume(a.size == 8)
-
assume(a.exists(_ == 8))
At this time, any other form of expression will just get a TestCanceledException
with message saying the given
expression was false. In the future, we will enhance this macro to give helpful error messages in more situations.
In ScalaTest 2.0, however, this behavior was sufficient to allow the ===
that returns Boolean
to be the default in tests. This makes ===
consistent between tests and production
code.
- Value parameters:
- condition
the boolean condition to assume
- Throws:
- TestCanceledException
if the condition is
false
.
- Inherited from:
- Assertions
Throws TestCanceledException
, with the passed
Throwable
cause, to indicate a test failed.
The getMessage
method of the thrown TestCanceledException
will return cause.toString
.
Throws TestCanceledException
, with the passed
Throwable
cause, to indicate a test failed.
The getMessage
method of the thrown TestCanceledException
will return cause.toString
.
- Value parameters:
- cause
a
Throwable
that indicates the cause of the cancellation.
- Throws:
- NullArgumentException
if
cause
isnull
- Inherited from:
- Assertions
Throws TestCanceledException
, with the passed
String
message
as the exception's detail
message and Throwable
cause, to indicate a test failed.
Throws TestCanceledException
, with the passed
String
message
as the exception's detail
message and Throwable
cause, to indicate a test failed.
- Value parameters:
- cause
A
Throwable
that indicates the cause of the failure.- message
A message describing the failure.
- Throws:
- NullArgumentException
if
message
orcause
isnull
- Inherited from:
- Assertions
Throws TestCanceledException
, with the passed
String
message
as the exception's detail
message, to indicate a test was canceled.
Throws TestCanceledException
, with the passed
String
message
as the exception's detail
message, to indicate a test was canceled.
- Value parameters:
- message
A message describing the cancellation.
- Throws:
- NullArgumentException
if
message
isnull
- Inherited from:
- Assertions
Throws TestCanceledException
to indicate a test was canceled.
Throws TestCanceledException
to indicate a test was canceled.
- Inherited from:
- Assertions
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals
Returns an Equality[A]
for any type A
that determines equality
by first calling .deep
on any Array
(on either the left or right side),
then comparing the resulting objects with ==
.
Returns an Equality[A]
for any type A
that determines equality
by first calling .deep
on any Array
(on either the left or right side),
then comparing the resulting objects with ==
.
- Returns:
a default
Equality
for typeA
- Inherited from:
- TripleEqualsSupport
This method enables the following syntax:
This method enables the following syntax:
result should equal (7) ^
The left should equal (right)
syntax works by calling ==
on the left
value, passing in the right
value, on every type except arrays. If both left
and right are arrays, deep
will be invoked on both left
and right
before comparing them with ==. Thus, even though this expression
will yield false, because Array
's equals
method compares object identity:
Array(1, 2) == Array(1, 2) // yields false
The following expression will not result in a TestFailedException
, because ScalaTest will compare
the two arrays structurally, taking into consideration the equality of the array's contents:
Array(1, 2) should equal (Array(1, 2)) // succeeds (i.e., does not throw TestFailedException)
If you ever do want to verify that two arrays are actually the same object (have the same identity), you can use the
be theSameInstanceAs
syntax.
- Inherited from:
- MatcherWords
Throws TestFailedException
, with the passed
Throwable
cause, to indicate a test failed.
The getMessage
method of the thrown TestFailedException
will return cause.toString
.
Throws TestFailedException
, with the passed
Throwable
cause, to indicate a test failed.
The getMessage
method of the thrown TestFailedException
will return cause.toString
.
- Value parameters:
- cause
a
Throwable
that indicates the cause of the failure.
- Throws:
- NullArgumentException
if
cause
isnull
- Inherited from:
- Assertions
Throws TestFailedException
, with the passed
String
message
as the exception's detail
message and Throwable
cause, to indicate a test failed.
Throws TestFailedException
, with the passed
String
message
as the exception's detail
message and Throwable
cause, to indicate a test failed.
- Value parameters:
- cause
A
Throwable
that indicates the cause of the failure.- message
A message describing the failure.
- Throws:
- NullArgumentException
if
message
orcause
isnull
- Inherited from:
- Assertions
Throws TestFailedException
, with the passed
String
message
as the exception's detail
message, to indicate a test failed.
Throws TestFailedException
, with the passed
String
message
as the exception's detail
message, to indicate a test failed.
- Value parameters:
- message
A message describing the failure.
- Throws:
- NullArgumentException
if
message
isnull
- Inherited from:
- Assertions
Throws TestFailedException
to indicate a test failed.
Throws TestFailedException
to indicate a test failed.
- Inherited from:
- Assertions
Intercept and return an exception that's expected to
be thrown by the passed function value. The thrown exception must be an instance of the
type specified by the type parameter of this method. This method invokes the passed
function. If the function throws an exception that's an instance of the specified type,
this method returns that exception. Else, whether the passed function returns normally
or completes abruptly with a different exception, this method throws TestFailedException
.
Intercept and return an exception that's expected to
be thrown by the passed function value. The thrown exception must be an instance of the
type specified by the type parameter of this method. This method invokes the passed
function. If the function throws an exception that's an instance of the specified type,
this method returns that exception. Else, whether the passed function returns normally
or completes abruptly with a different exception, this method throws TestFailedException
.
Note that the type specified as this method's type parameter may represent any subtype of
AnyRef
, not just Throwable
or one of its subclasses. In
Scala, exceptions can be caught based on traits they implement, so it may at times make sense
to specify a trait that the intercepted exception's class must mix in. If a class instance is
passed for a type that could not possibly be used to catch an exception (such as String
,
for example), this method will complete abruptly with a TestFailedException
.
Also note that the difference between this method and assertThrows
is that this method
returns the expected exception, so it lets you perform further assertions on
that exception. By contrast, the assertThrows
method returns Succeeded
, which means it can
serve as the last statement in an async- or safe-style suite. assertThrows
also indicates to the reader
of the code that nothing further is expected about the thrown exception other than its type.
The recommended usage is to use assertThrows
by default, intercept
only when you
need to inspect the caught exception further.
- Value parameters:
- classTag
an implicit
ClassTag
representing the type of the specified type parameter.- f
the function value that should throw the expected exception
- Returns:
the intercepted exception, if it is of the expected type
- Throws:
- TestFailedException
if the passed function does not complete abruptly with an exception that's an instance of the specified type.
- Inherited from:
- Assertions
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals
This field enables the following syntax:
This field enables the following syntax:
noException should be thrownBy ^
- Inherited from:
- MatcherWords
Throws TestPendingException
to indicate a test is pending.
Throws TestPendingException
to indicate a test is pending.
A pending test is one that has been given a name but is not yet implemented. The purpose of pending tests is to facilitate a style of testing in which documentation of behavior is sketched out before tests are written to verify that behavior (and often, the before the behavior of the system being tested is itself implemented). Such sketches form a kind of specification of what tests and functionality to implement later.
To support this style of testing, a test can be given a name that specifies one
bit of behavior required by the system being tested. The test can also include some code that
sends more information about the behavior to the reporter when the tests run. At the end of the test,
it can call method pending
, which will cause it to complete abruptly with TestPendingException
.
Because tests in ScalaTest can be designated as pending with TestPendingException
, both the test name and any information
sent to the reporter when running the test can appear in the report of a test run. (In other words,
the code of a pending test is executed just like any other test.) However, because the test completes abruptly
with TestPendingException
, the test will be reported as pending, to indicate
the actual test, and possibly the functionality it is intended to test, has not yet been implemented.
Note: This method always completes abruptly with a TestPendingException
. Thus it always has a side
effect. Methods with side effects are usually invoked with parentheses, as in pending()
. This
method is defined as a parameterless method, in flagrant contradiction to recommended Scala style, because it
forms a kind of DSL for pending tests. It enables tests in suites such as FunSuite
or FunSpec
to be denoted by placing "(pending)
" after the test name, as in:
test("that style rules are not laws") (pending)
Readers of the code see "pending" in parentheses, which looks like a little note attached to the test name to indicate
it is pending. Whereas "(pending())
looks more like a method call, "(pending)
" lets readers
stay at a higher level, forgetting how it is implemented and just focusing on the intent of the programmer who wrote the code.
- Inherited from:
- Assertions
Execute the passed block of code, and if it completes abruptly, throw TestPendingException
, else
throw TestFailedException
.
Execute the passed block of code, and if it completes abruptly, throw TestPendingException
, else
throw TestFailedException
.
This method can be used to temporarily change a failing test into a pending test in such a way that it will
automatically turn back into a failing test once the problem originally causing the test to fail has been fixed.
At that point, you need only remove the pendingUntilFixed
call. In other words, a
pendingUntilFixed
surrounding a block of code that isn't broken is treated as a test failure.
The motivation for this behavior is to encourage people to remove pendingUntilFixed
calls when
there are no longer needed.
This method facilitates a style of testing in which tests are written before the code they test. Sometimes you may
encounter a test failure that requires more functionality than you want to tackle without writing more tests. In this
case you can mark the bit of test code causing the failure with pendingUntilFixed
. You can then write more
tests and functionality that eventually will get your production code to a point where the original test won't fail anymore.
At this point the code block marked with pendingUntilFixed
will no longer throw an exception (because the
problem has been fixed). This will in turn cause pendingUntilFixed
to throw TestFailedException
with a detail message explaining you need to go back and remove the pendingUntilFixed
call as the problem orginally
causing your test code to fail has been fixed.
- Value parameters:
- f
a block of code, which if it completes abruptly, should trigger a
TestPendingException
- Throws:
- TestPendingException
if the passed block of code completes abruptly with an
Exception
orAssertionError
- Inherited from:
- Assertions
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals
Executes the block of code passed as the second parameter, and, if it
completes abruptly with a ModifiableMessage
exception,
prepends the "clue" string passed as the first parameter to the beginning of the detail message
of that thrown exception, then rethrows it. If clue does not end in a white space
character, one space will be added
between it and the existing detail message (unless the detail message is
not defined).
Executes the block of code passed as the second parameter, and, if it
completes abruptly with a ModifiableMessage
exception,
prepends the "clue" string passed as the first parameter to the beginning of the detail message
of that thrown exception, then rethrows it. If clue does not end in a white space
character, one space will be added
between it and the existing detail message (unless the detail message is
not defined).
This method allows you to add more information about what went wrong that will be reported when a test fails. Here's an example:
withClue("(Employee's name was: " + employee.name + ")") { intercept[IllegalArgumentException] { employee.getTask(-1) } }
If an invocation of intercept
completed abruptly with an exception, the resulting message would be something like:
(Employee's name was Bob Jones) Expected IllegalArgumentException to be thrown, but no exception was thrown
- Throws:
- NullArgumentException
if the passed
clue
isnull
- Inherited from:
- Assertions
Deprecated and Inherited methods
- Deprecated
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals
- Deprecated
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals
- Deprecated
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals
- Deprecated
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals
Trap and return any thrown exception that would normally cause a ScalaTest test to fail, or create and return a new RuntimeException
indicating no exception is thrown.
Trap and return any thrown exception that would normally cause a ScalaTest test to fail, or create and return a new RuntimeException
indicating no exception is thrown.
This method is intended to be used in the Scala interpreter to eliminate large stack traces when trying out ScalaTest assertions and
matcher expressions. It is not intended to be used in regular test code. If you want to ensure that a bit of code throws an expected
exception, use intercept
, not trap
. Here's an example interpreter session without trap
:
scala> import org.scalatest._ import org.scalatest._ scala> import Matchers._ import Matchers._ scala> val x = 12 a: Int = 12 scala> x shouldEqual 13 org.scalatest.exceptions.TestFailedException: 12 did not equal 13 at org.scalatest.Assertions$class.newAssertionFailedException(Assertions.scala:449) at org.scalatest.Assertions$.newAssertionFailedException(Assertions.scala:1203) at org.scalatest.Assertions$AssertionsHelper.macroAssertTrue(Assertions.scala:417) at .<init>(<console>:15) at .<clinit>(<console>) at .<init>(<console>:7) at .<clinit>(<console>) at $print(<console>) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at scala.tools.nsc.interpreter.IMain$ReadEvalPrint.call(IMain.scala:731) at scala.tools.nsc.interpreter.IMain$Request.loadAndRun(IMain.scala:980) at scala.tools.nsc.interpreter.IMain.loadAndRunReq$1(IMain.scala:570) at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:601) at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:565) at scala.tools.nsc.interpreter.ILoop.reallyInterpret$1(ILoop.scala:745) at scala.tools.nsc.interpreter.ILoop.interpretStartingWith(ILoop.scala:790) at scala.tools.nsc.interpreter.ILoop.command(ILoop.scala:702) at scala.tools.nsc.interpreter.ILoop.processLine$1(ILoop.scala:566) at scala.tools.nsc.interpreter.ILoop.innerLoop$1(ILoop.scala:573) at scala.tools.nsc.interpreter.ILoop.loop(ILoop.scala:576) at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply$mcZ$sp(ILoop.scala:867) at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply(ILoop.scala:822) at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply(ILoop.scala:822) at scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135) at scala.tools.nsc.interpreter.ILoop.process(ILoop.scala:822) at scala.tools.nsc.MainGenericRunner.runTarget$1(MainGenericRunner.scala:83) at scala.tools.nsc.MainGenericRunner.process(MainGenericRunner.scala:96) at scala.tools.nsc.MainGenericRunner$.main(MainGenericRunner.scala:105) at scala.tools.nsc.MainGenericRunner.main(MainGenericRunner.scala)
That's a pretty tall stack trace. Here's what it looks like when you use trap
:
scala> trap { x shouldEqual 13 } res1: Throwable = org.scalatest.exceptions.TestFailedException: 12 did not equal 13
Much less clutter. Bear in mind, however, that if no exception is thrown by the
passed block of code, the trap
method will create a new NormalResult
(a subclass of Throwable
made for this purpose only) and return that. If the result was the Unit
value, it
will simply say that no exception was thrown:
scala> trap { x shouldEqual 12 } res2: Throwable = No exception was thrown.
If the passed block of code results in a value other than Unit
, the NormalResult
's toString
will print the value:
scala> trap { "Dude!" } res3: Throwable = No exception was thrown. Instead, result was: "Dude!"
Although you can access the result value from the NormalResult
, its type is Any
and therefore not
very convenient to use. It is not intended that trap
be used in test code. The sole intended use case for trap
is decluttering
Scala interpreter sessions by eliminating stack traces when executing assertion and matcher expressions.
- Deprecated
- Inherited from:
- Assertions
Concrete fields
This field enables the following syntax:
This field enables the following syntax:
badBook must not be a ('goodRead) ^
This field enables the following syntax:
This field enables the following syntax:
badBook must not be an (excellentRead) ^
This field enables the following syntax:
This field enables the following syntax:
map must not contain key (10) ^
This field enables the following syntax:
This field enables the following syntax:
"eight" must not fullyMatch regex ("""(-)?(\d+)(\.\d*)?""".r) ^
Inherited fields
This field enables syntax such as the following:
This field enables syntax such as the following:
result should equal ("hello") (after being lowerCased) ^
- Inherited from:
- Explicitly
This field enables syntax such as the following:
This field enables syntax such as the following:
obj should (be theSameInstanceAs (string) and be theSameInstanceAs (string)) ^
- Inherited from:
- MatcherWords
This field enables the following syntax:
This field enables the following syntax:
"val a: String = 1" shouldNot compile ^
- Inherited from:
- MatcherWords
This field enables syntax such as the following:
This field enables syntax such as the following:
list should (contain ('a') and have length (7)) ^
- Inherited from:
- MatcherWords
This field enables syntax such as the following:
This field enables syntax such as the following:
result should equal ("hello") (decided by defaultEquality) ^
- Inherited from:
- Explicitly
This field enables the following syntax:
This field enables the following syntax:
seq should be (defined) ^
- Inherited from:
- MatcherWords
This field enables syntax such as the following, given an
Equivalence[String]
named myStringEquivalence
:
This field enables syntax such as the following, given an
Equivalence[String]
named myStringEquivalence
:
result should equal ("hello") (determined by myStringEquivalence) ^
- Inherited from:
- Explicitly
This field enables the following syntax:
This field enables the following syntax:
list should be (empty) ^
- Inherited from:
- MatcherWords
This field enables syntax such as the following:
This field enables syntax such as the following:
string should (endWith ("ago") and include ("score")) ^
- Inherited from:
- MatcherWords
This field enables the following syntax:
This field enables the following syntax:
file should exist ^
- Inherited from:
- MatcherWords
This field enables syntax such as the following:
This field enables syntax such as the following:
string should (fullyMatch regex ("Hel*o, wor.d") and not have length (99)) ^
- Inherited from:
- MatcherWords
This field enables syntax such as the following:
This field enables syntax such as the following:
list should (have length (3) and not contain ('a')) ^
- Inherited from:
- MatcherWords
This field enables syntax such as the following:
This field enables syntax such as the following:
string should (include ("hope") and not startWith ("no")) ^
- Inherited from:
- MatcherWords
This field enables the following syntax:
This field enables the following syntax:
"hi" should not have length (3) ^
- Inherited from:
- MatcherWords
This field enables the following syntax:
This field enables the following syntax:
result should matchPattern { case Person("Bob", _) => } ^
- Inherited from:
- MatcherWords
This field enables syntax like the following:
This field enables syntax like the following:
myFile should (not be an (directory) and not have ('name ("foo.bar"))) ^
- Inherited from:
- MatcherWords
This field enables the following syntax:
This field enables the following syntax:
file should be (readable) ^
- Inherited from:
- MatcherWords
This field enables the following syntax:
This field enables the following syntax:
set should not have size (3) ^
- Inherited from:
- MatcherWords
This field enables the following syntax:
This field enables the following syntax:
seq should be (sorted) ^
- Inherited from:
- MatcherWords
This field enables syntax such as the following:
This field enables syntax such as the following:
string should (startWith ("Four") and include ("year")) ^
- Inherited from:
- MatcherWords
The Succeeded
singleton.
The Succeeded
singleton.
You can use succeed
to solve a type error when an async test
does not end in either Future[Assertion]
or Assertion
.
Because Assertion
is a type alias for Succeeded.type
,
putting succeed
at the end of a test body (or at the end of a
function being used to map the final future of a test body) will solve
the type error.
- Inherited from:
- Assertions
This field enables the following syntax:
This field enables the following syntax:
"val a: String = 1" shouldNot typeCheck ^
- Inherited from:
- MatcherWords
Extensions
Extensions
This method enables syntax such as the following:
This method enables syntax such as the following:
string mustNot typeCheck ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string mustNot compile ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string mustNot fullyMatch regex ("""(-)?(\d+)(\.\d*)?""") ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string must compile ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string must fullyMatch regex ("""(-)?(\d+)(\.\d*)?""") ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result must equal (3) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustBe defined ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string mustNot endWith regex ("world") ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustNot (be readable) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustEqual null ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustNot have length (3) ^ result mustNot have size (3) ^ exception mustNot have message ("file not found") ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string must include regex ("hi") ^
This method enables the following syntax:
This method enables the following syntax:
list mustBe a ('empty) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string must startWith regex ("hello") ^
This method enables the following syntax, where excellentRead
refers to a BePropertyMatcher[Book]
:
This method enables the following syntax, where excellentRead
refers to a BePropertyMatcher[Book]
:
programmingInScala mustBe an (excellentRead) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustBe theSameInstanceAs (anotherObject) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustBe writable ^
This method enables syntax such as the following:
This method enables syntax such as the following:
file must exist ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result must have length (3) ^ result must have size (3) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
file must not (exist) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result must not equal (3) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustBe empty ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result must === (100 +- 1) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string mustNot include regex ("hi") ^
This method enables the following syntax:
This method enables the following syntax:
list mustBe 'empty ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string must endWith regex ("world") ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustBe sorted ^
This method enables syntax such as the following:
This method enables syntax such as the following:
string mustNot startWith regex ("hello") ^
This method enables syntax such as the following:
This method enables syntax such as the following:
aDouble mustBe an [Book] ^
This method enables the following syntax, where excellentRead
refers to a BePropertyMatcher[Book]
:
This method enables the following syntax, where excellentRead
refers to a BePropertyMatcher[Book]
:
programmingInScala mustBe excellentRead ^
This method enables syntax such as the following:
This method enables syntax such as the following:
8 mustBe > (7) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
aDouble mustBe a [Book] ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result must (equal (expected) and have length 3) ^
This method enables the following syntax:
This method enables the following syntax:
list mustBe an ('empty) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
a mustEqual b ^
This method enables syntax such as the following:
This method enables syntax such as the following:
5 mustBe < (7) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
5 mustBe <= (7) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
a must === (b) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
aDouble mustBe 8.8 ^
This method enables syntax such as the following:
This method enables syntax such as the following:
8 mustBe >= (7) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
file mustNot exist ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustBe null ^
This method enables syntax such as the following:
This method enables syntax such as the following:
xs must contain oneOf (1, 2, 3) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustBe readable ^
This method enables syntax such as the following:
This method enables syntax such as the following:
xs mustNot contain (oneOf (1, 2, 3)) ^
This method enables the following syntax, where goodRead
refers to a BePropertyMatcher[Book]
:
This method enables the following syntax, where goodRead
refers to a BePropertyMatcher[Book]
:
programmingInScala mustBe a (goodRead) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustNot (be (3)) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result mustNot be (3) ^
This method enables syntax such as the following:
This method enables syntax such as the following:
result must be a aMatcher ^
Inherited extensions
Implicits
Implicits
This implicit conversion method converts a Symbol
to a
HavePropertyMatcherGenerator
, to enable the symbol to be used with the have ('author ("Dickens"))
syntax.
This implicit conversion method converts a Symbol
to a
HavePropertyMatcherGenerator
, to enable the symbol to be used with the have ('author ("Dickens"))
syntax.
Inherited implicits
Implicitly converts an object of a Numeric
type to a PlusOrMinusWrapper
,
to enable a +-
method to be invoked on that object.
Implicitly converts an object of a Numeric
type to a PlusOrMinusWrapper
,
to enable a +-
method to be invoked on that object.
- Inherited from:
- Tolerance
Implicitly converts an object of type String
to a StringMustWrapper
,
to enable must
methods to be invokable on that object.
Implicitly converts an object of type String
to a StringMustWrapper
,
to enable must
methods to be invokable on that object.
- Inherited from:
- MustVerb
- Definition Classes
- TripleEquals -> TripleEqualsSupport
- Inherited from:
- TripleEquals