Minitest
A mini testing framework cross-compiled for Scala 2.12, 2.13, 3.0, and Scala.JS 1.x.
Usage in SBT
For build.sbt
(use the %%%
operator for Scala.js):
// use the %%% operator for Scala.js
libraryDependencies += "io.monix" %% "minitest" % "2.9.6" % "test"
testFrameworks += new TestFramework("minitest.runner.Framework")
In case you want the optional package for integration with the latest ScalaCheck, at the moment of writing this being version 1.15.4
:
// use the %%% operator for Scala.js
libraryDependencies += "io.monix" %% "minitest-laws" % "2.9.6" % "test"
Given that updates for ScalaCheck have been problematic, the ecosystem being at the moment of writing using an older version, a "legacy" package is currently provided for usage with ScalaCheck 1.13.5
:
// use the %%% operator for Scala.js
libraryDependencies += "io.monix" %% "minitest-laws-legacy" % "2.7.0" % "test"
Note that at this time the laws package is not available for Scala Native, due to ScalaCheck not being available for it.
Tutorial
Test suites MUST BE objects, not classes. To create a simple test suite, it could inherit from SimpleTestSuite:
Here's a simple test:
import minitest._
object MySimpleSuite extends SimpleTestSuite {
test("should be") {
assertEquals(2, 1 + 1)
}
test("should not be") {
assert(1 + 1 != 3)
}
test("should throw") {
class DummyException extends RuntimeException("DUMMY")
def test(): String = throw new DummyException
intercept[DummyException] {
test()
}
()
}
test("test result of") {
assertResult("hello world") {
"hello" + " " + "world"
}
}
}
In case you want to setup an environment for each test and need setup
and tearDown
semantics, per test, you could inherit from TestSuite. Then on each test
definition, you'll receive a fresh value:
import minitest.TestSuite
object MyTestSuite extends TestSuite[Int] {
def setup(): Int = {
Random.nextInt(100) + 1
}
def tearDown(env: Int): Unit = {
assert(env > 0, "should still be positive")
}
test("should be positive") { env =>
assert(env > 0, "positive test")
}
test("should be lower or equal to 100") { env =>
assert(env <= 100, s"$env > 100")
}
}
Some tests require setup and tear down logic to happen only once per test suite being executed and TestSuite
supports that as well, but note you should abstain from doing this unless you really need it, since the per test semantics are much saner:
object MyTestSuite extends TestSuite[Int] {
private var system: ActorSystem = _
override def setupSuite(): Unit = {
system = ActorSystem.create()
}
override def tearDownSuite(): Unit = {
TestKit.shutdownActorSystem(system)
system = null
}
}
Minitest supports asynchronous results in tests, just use testAsync
and return a Future[Unit]
:
import scala.concurrent.ExecutionContext.Implicits.global
object MySimpleSuite extends SimpleTestSuite {
testAsync("asynchronous execution") {
val future = Future(100).map(_+1)
for (result <- future) yield {
assertEquals(result, 101)
}
}
}
Minitest has integration with ScalaCheck. So for property-based testing:
import minitest.laws.Checkers
object MyLawsTest extends SimpleTestSuite with Checkers {
test("addition of integers is commutative") {
check2((x: Int, y: Int) => x + y == y + x)
}
test("addition of integers is associative") {
check3((x: Int, y: Int, z: Int) => (x + y) + z == x + (y + z))
}
}
All available assertions are described in minitest.api.Asserts:
// Simple boolean testing
assert(value == expected)
// ... and with a message
assert(value == expected, s"value: $value == expected $expected")
// Equality testing
assertEquals(value, expected)
// Tests the result of an entire block of code
assertResult("Hello, World!") {
Seq("Hello", "World").mkString(", ") + "!"
}
// ... and with a hint
assertResult("Hello, World!", "No hello?!?") {
Seq("Hello", "World").mkString(", ") + "!"
}
// Tests that code throws some specific exception
intercept[IllegalStateException] {
// ...
throw new IllegalStateException("boom!")
}
// Tests that a specific piece of code does not compile
assertDoesNotCompile("1.noSuchMethod")
// Tests that compilation fails for a piece of code with
// a specific error message (via regular expression)
assertDoesNotCompile("1.noSuchMethod", ".*?noSuchMethod is not a member of Int")
// Ignores a piece of test, could be conditional
if (isEnvironmentJavaScript) {
ignore("Test not available on top of JavaScript")
}
// Cancels a test — same as ignoring, but slightly different meaning;
// same result though
if (isEnvironmentJavaScript) {
cancel("Test cannot proceed on top of JavaScript")
}
// Fails a test immediately
fail("Boom!")
That's all you need to know.
License
All code in this repository is licensed under the Apache License, Version 2.0. See LICENCE.
Copyright © 2014-2018 by The Minitest Project Developers.