Source locations for errors
Test failures point to the source code location where the failure happened. Cmd+click on the filename to open the relevant line number in your editor (does not work in all terminals).
Assertion failures show the difference between the expected and obtained behavior. Diffs for case classes include field names in Scala 2.13.
Highlighted stack traces
Classes that are defined in your workspace are highlighted in stack traces making it easier to quickly understand an error.
Run MUnit test suites directly from the comfort of your IDE, whether it's IntelliJ, VS Code, or any other LSP editor.