You can use the assertions provided by this trait in any ScalaTest Suite, because Suite mixes in this trait. This trait is designed to be used independently of anything else in ScalaTest, though, so you can mix it into anything. (You can alternatively import the methods defined in this trait. For details, see the documentation for the Assertions companion object.

In any Scala program, you can write assertions by invoking assert and passing in a Boolean expression, such as:

 val left = 2
 val right = 1
 assert(left == right)
 

If the passed expression is true, assert will return normally. If false, assert will complete abruptly with an AssertionError. This behavior is provided by the assert method defined in object Predef, whose members are implicitly imported into every Scala source file. This Assertions traits defines another assert method that hides the one in Predef. It behaves the same, except that if false is passed it throws TestFailedException instead of AssertionError. The reason it throws TestFailedException is because TestFailedException carries information about exactly which item in the stack trace represents the line of test code that failed, which can help users more quickly find an offending line of code in a failing test.

If you pass the previous Boolean expression, left == right to assert in a ScalaTest test, a failure will be reported, but without reporting the left and right values. You can alternatively encode these values in a String passed as a second argument to assert, like this:

 val left = 2
 val right = 1
 assert(left == right, left + " did not equal " + right)
 

Using this form of assert, the failure report will include the left and right values, thereby helping you debug the problem. However, ScalaTest provides the === operator to make this easier. You use it like this:

 val left = 2
 val right = 1
 assert(left === right)
 

Because you use === here instead of ==, the failure report will include the left and right values. For example, the detail message in the thrown TestFailedException from the assert shown previously will include, "2 did not equal 1". From this message you will know that the operand on the left had the value 2, and the operand on the right had the value 1.

If you're familiar with JUnit, you would use === in a ScalaTest Suite where you'd use assertEquals in a JUnit TestCase. The === operator is made possible by an implicit conversion from Any to Equalizer. If you're curious to understand the mechanics, see the documentation for Equalizer and the convertToEqualizer method.

Expected results

 val a = 5
 val b = 2
 expect(2) {
   a - b
 }
 

In this case, the expected value is 2, and the code being tested is a - b. This expectation will fail, and the detail message in the TestFailedException will read, "Expected 2, but got 3."

Intercepted 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. You can do this in the JUnit 3 style, like this:

 val s = "hi"
 try {
   s.charAt(-1)
   fail()
 }
 catch {
   case _: IndexOutOfBoundsException => // Expected, so continue
 }
 

If charAt throws IndexOutOfBoundsException as expected, control will transfer to the catch case, which does nothing. If, however, charAt fails to throw an exception, the next statement, fail(), will be run. The fail method always completes abruptly with a TestFailedException, thereby signaling a failed test.

To make this common use case easier to express and read, ScalaTest provides an intercept method. You use it like this:

 val s = "hi"
 intercept[IndexOutOfBoundsException] {
   s.charAt(-1)
 }
 

This code behaves much like the previous example. If charAt throws an instance of IndexOutOfBoundsException, intercept will return that exception. But if charAt completes normally, or throws a different exception, intercept will complete abruptly with a TestFailedException. intercept 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.