Powerful, elegant and flexible test framework for Kotlin with additional assertions, property testing and data driven testing
Long
assertions and property testers by @RusticFlare in https://github.com/kotest/kotest/pull/3720
BigDecimal.ZERO.shouldBePositive()
returning true by @pubiqq in https://github.com/kotest/kotest/pull/3814
intersect
matcher to ranges by @AlexCue987 in https://github.com/kotest/kotest/pull/3792
shouldNotBePositive
and shouldNotBeNegative
matchers for BigDecimal by @pubiqq in https://github.com/kotest/kotest/pull/3818
Iterable
in withData
on root level by @obecker in https://github.com/kotest/kotest/pull/3831
shouldBe expected
equivalent to should be(expected)
for non-matcher objects by @pubiqq in https://github.com/kotest/kotest/pull/3827
Full Changelog: https://github.com/kotest/kotest/compare/v5.8.0...v5.8.1
Full Changelog: https://github.com/kotest/kotest/compare/v5.7.2...v5.8.0
Arb.string()
to only generate Strings of printable ascii characters
Arb.string()
With Kotest 5.6.0, Codepoint.ascii()
was changed to include a wider range of ascii chararacters, and Codepoint.printableAscii()
was introduced with the historic range used by Codepoint.ascii()
.
Arb.string()
has been using Codepoint.ascii()
as it's default for generating chars for the string. This caused issues for some users, and we decided to revert Arb.string()
to the historic behavior by changing the default to the new Codepoint.printableAscii()
.
Hopefully this doesn't cause any issues for you. If it does, you can revert to the 5.6.0 ~ 5.6.1 behavior by using Codepoint.ascii()
explicitly.
If you added explicit usage of Codepoint.printableAscii()
to circumvent the issue, you can safely remove the explicit parameter starting with Kotest 5.6.2.
Full Changelog: https://github.com/kotest/kotest/compare/v5.6.1...v5.6.2
Maintenance release, published since 5.6.0 failed to upload for some targets.
ConstantNow
-related functions to a new module named io.kotest:kotest-extensions-now
(remember to add -jvm suffix for Maven)
withConstantNow
See full changelog at https://kotest.io/docs/changelog.html
ConstantNow
-related functions to a new module named io.kotest:kotest-extensions-now
(remember to add -jvm suffix for Maven)
withConstantNow
See full changelog at https://kotest.io/docs/changelog.html
Fixes issue 3277.
gradle test --tests "A*" --tests "B*"
All tests from A* and B* were skipped instead of being ran.
This was a regression from 5.4.x, where this used to work. This was because kotest 5.5.3 were using the wrong combinators for combining the inclusion filters.
Contributors: