[*] I know this is probably a bit late, but ScalaTest provides this feature out of the box (I believe since version 2) by mixing in the ScalaFutures trait, or using it directly in your test functions. Behold! test(“some test”) { val f: Future[Something] = someObject.giveMeAFuture ScalaFutures.whenReady(f.failed) { e => e shouldBe a [SomeExceptionType] } … Read more
The intended way to do this is to use nested suites. Suite has a nestedSuites method that returns an IndexedSeq[Suite] (in 2.0, in 1.9.1 it was a List[Suite]). Suite also has a runNestedSuites method that is responsible for executing any nested suites. By default runNestedSuites calls nestedSuites, and on each returned Suite either invokes run … Read more
You’re the first to ask for such a feature. One way to achieve this is with withClue. Something like: withClue(“NumberOfElements: “) { NumberOfElements() should be (5) } That should get you this error message: NumberOfElements: 10 was not equal to 5 If you want to control the message completely you can write a custom matcher. … Read more
Scala is not Java. Scala just does not have the operator instanceof instead it has a parametric method called isInstanceOf[Type]. You might also enjoy watching a ScalaTest Crash Course.
Specs and ScalaTest are both good tools with happy users, but they differ in several ways. You will probably want to pick one as your main testing tool in Scala, but need not give up the other because you can use pieces of both. If you like ScalaTest’s FeatureSpec syntax and specs’ Mockito syntax, for … Read more
This is now supported (since ScalaTest 2.1.3) within interactive mode: testOnly *MySuite — -z foo to run only the tests whose name includes the substring “foo”. For exact match rather than substring, use -t instead of -z. If you run it from the command line, it should be as single argument to sbt: sbt ‘testOnly … Read more