Skip to content

Releases: typelevel/scalacheck

Scalacheck 1.15.0

31 Oct 15:43
1.15.0
ef74177

Choose a tag to compare

Compatibility

  • Binary compatible with 1.14.3 version of ScalaCheck.

  • Source incompatible type signatures of Gen.atLeastOne and Gen.someOf in Scala 2.13 artifact(s) of 1.14.3 version of ScalaCheck that will be fixed in 1.15.1.

Changed

  • Dropped support for Scala 2.10.x

  • Remove implicit for Prop.BooleanOperators which was deprecated in 1.14.1 in favor of Prop.propBoolean #667

  • Added support for Dotty (currently 0.27)

  • Various improvements to Gen and Arbitrary #575

  • Improvements to Char and String generators #653

  • Single-argument Prop.collect is deprecated #449

Fixed

  • Prevent nesting properties #677

  • Seed with four zeroes is not allowed #674

  • Printing order of shrunk values #635

  • Initial seed was reused #651

Added

  • Choose[BigDecimal] #670

  • Choose[BigInt] #636

  • Statistical distributions (e.g. Gaussian, Poisson) #656

  • Shrinking with LazyList for Scala 2.13 compatibility #626 #627

  • Shrink.suchThat #484

  • Gen.recursive for recursive generators #616 #639

This release was brought to you by 16 contributors, according to git shortlog -sn --no-merges 1.14.3..1.15.0. Thank you Scala Steward, Aaron S. Hawley, Erik Osheim, Lars Hupel, Dolan Murvihill, Alexey Kotlyarov, Zak, Seth Tisue, Taro L. Saito, Neville Li, P. Oscar Boykin, Guillaume Martres, Sean C. Sullivan, Fred Roth, Jonas Kölker, NthPortal.

ScalaCheck 1.14.3

14 Dec 16:53
6464e98

Choose a tag to compare

Release notes

ScalaCheck 1.14.3 is a minor update from ScalaCheck 1.14.2, and it is binary compatible. This means that if you are using any other framework in combination with ScalaCheck, like ScalaTest or specs2 you can typically just bump the version of ScalaCheck in your build definition or wait for those libraries to transitively do it for you in their next update. You still need to make sure that the combination of frameworks you are using was built and tested together with each other, otherwise you can run into errors related to binary compatibility that are possibly very hard to debug.

If you're using ScalaCheck as your only testing framework, you can safely update your build definition to use the latest ScalaCheck release, although you might not see compilation errors but there may be deprecation warnings due to expected changes in ScalaCheck's API.

The detailed list of changes from the CHANGELOG for the 1.14.3. release are below.

Compatibility

  • Binary compatible with 1.14.2 version of ScalaCheck.

Changed

  • Update Scala.js to 1.0.0-RC2, previously was 1.0.0-M8.

  • Update Scala.js to 0.6.31, previously was 0.6.29.

Fixed

  • Ensure posNum and negNum always return values #568

Added

  • No added features.

ScalaCheck 1.14.2

25 Sep 17:08

Choose a tag to compare

For a detailed list of changes, see the CHANGELOG for the 1.14.2 release.

ScalaCheck 1.14.1

18 Sep 04:49
@non non

Choose a tag to compare

For a detailed list of changes, see the CHANGELOG for the 1.14.1 release.