Edit

Troubleshooting

Print full stack traces

By default, MUnit trims exception stack traces to avoid printing redundant information to the console. Use the -F test framework flag to print full stack traces, which can be helpful when debugging a cryptic error.

In sbt, test framework flags can be passed to the testOnly task.

$ sbt
> myproject/testOnly -- -F

Invalid test class

If you define a test suite as an object instead of class you get the following error:

==> X munit.BasicSuite.initializationError  0.003s org.junit.runners.model.InvalidTestClassError: Invalid test class 'munit.BasicSuite':
  1. Test class should have exactly one public constructor
  2. No runnable methods

To fix the problem, use class instead of object

- object MySuite extends munit.FunSuite { ... }
+ class MySuite extends munit.FunSuite { ... }