should and must are the same semantically. But it’s not about better documentation, it’s basically just down to personal stylistic preference (I prefer must for example). can is a little different. You can’t (nomen omen) use it directly as a matcher, it’s only available in a test descriptor. Quote from FlatSpec: Note: you can use … Read more
The easy way to do this in 1.8 is to add a constructor that takes a dummy argument. ScalaTest (and sbt) won’t discover the class if it doesn’t have a public, no-arg constructor: class MySuite(ignore: String) extends FunSuite { // … } In 2.0 you’ll be able to just write @Ignore on the class: @Ignore … Read more
your sbt build file is not right. your scala version is 2.12.x but you are using libraries compiled in scala version 2.11. use the sbt settings shown below note: I changed the version of scalatest as 2.x versions are no longer supported for 2.12 version of scala scalaVersion := “2.12.1” libraryDependencies ++= Seq( “org.scala-js” %% … Read more
The current version of ScalaTest does support this: noException should be thrownBy 0 / 1 See docs.
If you just want to redirect console output for a limited duration, use the withOut and withErr methods defined on Console: val stream = new java.io.ByteArrayOutputStream() Console.withOut(stream) { //all printlns in this block will be redirected println(“Fly me to the moon, let me play among the stars”) }
If you just added the dependency, it might not have been downloaded yet. Refresh/reimport the project to do so. If it has already been downloaded, press Alt+Enter in IntelliJ on the lines with the warning and select the “update project resolvers’ indexes” quickfix, then select the “local cache” index and click “update”. You can verify … Read more
Meanwhile you can use Iterable(2, 1) should contain theSameElementsAs Iterable(1, 2) To test the ordered set you have to convert it to a sequence. Set(1, 2).toSeq should contain theSameElementsInOrderAs List(1, 2)
This is the triple-equals operator from ScalaTest. Have a look at this page: Getting Started with FunSuite. It says: ScalaTest lets you use Scala’s assertion syntax, but defines a triple equals operator (===) to give you better error messages. The following code would give you an error indicating only that an assertion failed: assert(1 == … Read more
I am in the middle when it comes to testing everything. I don’t usually test everything, but sometimes it’s really useful to be able to unit test a private function without having to mangle my code to make it possible. If you’re using ScalaTest, you can use the PrivateMethodTester to do it. import org.scalatest.{ FlatSpec, … Read more
Using hints found in the documentation here: (quoted) You can configure the output shown when running with sbt in four ways: 1) turn off color, 2) show short stack traces, 3) full stack traces, and 4) show durations for everything. To do so you must pass a -o argument to ScalaTest, and after the -o, … Read more