Releases: scalameta/munit
MUnit v0.7.6
Bug fixes
This release contains several fixes to critical bugs that could cause failing tests to pass without an error message.
- Regenerate default seed at every prop iteration (#124) @gabro
assertEquals
would sometimes pass when it should fail (#125) @olafurpg- tests with duplicate name+tags+location would be silently ignored (#125) @olafurpg
- Fix Scala.js v1.0.0 linking error (#120) @tindzk
New features
By default, MUnit trims exception stack traces to avoid printing redundant
information to the console. Use the new -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
Pull requests
- Several combined fixes (#125) @olafurpg
- Update sbt-mdoc to 2.2.0 (#123) @scala-steward
- Add support for Dotty 0.23.0 (#117) @olafurpg
- Update sbt-scalafix to 0.9.15 (#110) @scala-steward
- Update sbt-ci-release to 1.5.3 (#111) @scala-steward
- Upgrade to latest Dotty and 2.13 (#115) @olafurpg
MUnit v0.7.3
Pull Requests
Docs
Scala Stweard
- Update sbt-scalafmt to 2.3.4 (#102) @scala-steward
- Update google-cloud-storage to 1.107.0 (#105) @scala-steward
- Update sbt to 1.3.10 (#106) @scala-steward
- Update sbt-scalafix to 0.9.14 (#104) @scala-steward
MUnit v0.7.2
Async FunFixture
Previously, FunFixture
only supported synchronous setup/teardown methods.
Now, the setup/teardown methods can also return Future[T]
values like this
val number = FunFixture.async[Int](
setup = _ => Future(...),
teardown = _ => Future(...)
)
The non-async new FunFixture[T]
constructor has now been deprecated in favor of an apply
constructor. To migrate existing usage
-- 0.7.1 (old version)
++ 0.7.2 (new version)
- new FunFixture[T](...)
+ FunFixture[T](...)
Thank you @2m for contributing this feature!
Pull requests
- Scalacheck blogpost (#77) @gabro
- Print property seeds and add docs about reproducing test failures (#90) @gabro
Library updates
- Update sbt-dotty to 0.4.1 (#99) @scala-steward
- Update sbt-scalafix to 0.9.13 (#94) @scala-steward
- Update sbt to 1.3.9 (#95) @scala-steward
- Update sbt-scalajs, scalajs-compiler, ... to 1.0.1 (#84) @scala-steward
- Update google-cloud-storage to 1.103.1 (#82) @scala-steward
- Update sbt-scalafix to 0.9.12 (#80) @scala-steward
- Update sbt to 1.3.8 (#85) @scala-steward
- Update sbt-mdoc to 2.1.5 (#86) @scala-steward
- Upd@scala-steward ease to 1.5.2 (#81) @scala-steward
MUnit v0.7.1
MUnit v0.7.0
MUnit v0.6.0
Pull Requests
- Add munit-scalacheck module (#71) @gabro
- Relax
assertEquals
strictness about type equality. (#70) @olafurpg - Update to Dotty v0.23 (#69) @gzoller
- Usually, MUnit is only needed in test. (#66) @takayahilton
- Use consistent solution to customize tests, suites and values (#64) @olafurpg
- Fix buggy filtering examples from blog post. (#63) @olafurpg
- Add failSuite() helper to abort the entire test suite (#59) @Daron666
MUnit v0.5.2
- #58 Add
compileErrors()
helper to assert against compile-time errors - #57 Add
def test(name: String)
overload for easier readability. - #55 Fix bug where test cases got reported as duplicates in IntelliJ.
- #54 Indent successful test case reports by two spaces.
Refactorings
- #53 Move junit-interface into the MUnit codebase.
NOTE: it may take a while for the artifacts to appear on Maven Central. Please ignore v0.5.1 since that release failed.
MUnit v0.5.0
MUnit v0.4.5
FunSuite v0.1.4
- Remove unused
BeforeAll
andAfterAll