munit - usability and stability for 1.0

[szymon-rd]

Context

This issue is meant to track the progress in improving the toolkit libraries' usability and stability. This issue is created here to establish the toolkit's perspective in the discussion, especially the interoperability between the toolkit's libraries and usability with the definition used in the Toolkit.

Tasks

Below is the list of high-priority issues. They all should have corresponding issues in the library's issue tracker when we start working on them. The discussions about the usability of the library within the Toolkit should take place here.

• [ ] Release stable version - https://github.com/scalameta/munit/issues/647

[bishabosha]

There was mention of adding junit 5 support also

[shardulc]

(Sorry if this is the wrong place for this comment!)

The latest release of scala-toolkit, 0.2.0, uses MUnit 1.0.0-M7. However, two significant bugs (in my opinion—biased because I was recently bitten by one of them, and the other seems related) have been fixed in MUnit since then:

• Handle a StackOverflowError in addition to NonFatal errors in v1.0.0-M8
• Fail test suites on fatal exceptions in v1.0.0-M9

Do you think these are significant enough to already update the version of MUnit included in scala-toolkit for the next release even before 1.0? BTW the latest release of MUnit is now v1.0.0-M10.

[armanbilge]

Do you think these are significant enough to already update the version of MUnit included in scala-toolkit for the next release

@shardulc see:

• https://github.com/scala/toolkit/issues/33

[SethTisue]

MUnit got out of milestones and into RCs a couple weeks ago, so that seems promising! https://github.com/scalameta/munit/releases/tag/v1.0.0-RC1