ScalaCheck Changelog

What's new in ScalaCheck 1.12.5

Sep 10, 2015
  • A maintenance release that primarily fixes issues in the sbt test runner that caused errors in the integration with ScalaTest and specs2.

New in ScalaCheck 1.12.3 (May 21, 2015)

  • Fixes a number of bugs since last version, and adds some new API methods. The SBT build definition has also been cleaned up so that more (all) code is shared between the JVM and JS builds. The SBT test runner has been improved to take advantage of more SBT-specific features. The JS support has been updated for Scala.JS 0.6.3.

New in ScalaCheck 1.12.2 (Feb 6, 2015)

  • Introduces support for ScalaJS 0.6.0, as well as a few minor fixes and additions.

New in ScalaCheck 1.12.1 (Dec 2, 2014)

  • Introduces a small change that hopefully improves compatibility for
  • projects moving from ScalaCheck 1.11.x. Otherwise, no API additions where made
  • since 1.12.0.
  • Also introduces experimental support for ScalaJS.

New in ScalaCheck 1.12.0 (Nov 26, 2014)

  • The big news in ScalaCheck 1.12.0 is a new implementation of the Commands API,
  • introduced at ScalaDays 2014 in Berlin.
  • Support for Scala 2.9 has been dropped in ScalaCheck 1.12.0. Only Scala 2.10
  • and 2.11 are supported now.
  • Other than that there has been minor fixes and improvements since 1.11.6. Also,
  • all methods and classes that were deprecated in 1.11.6 have now been removed
  • from ScalaCheck. So you might experience build errors if your code was out of
  • date with 1.11.6.
  • The type signature of Gen.sequence has been slightly changed (generalised), and
  • the Gen.containerOf[C[_,_],T]-methods have been removed. It you used them you
  • should now use one of the more general Gen.buildableOf-methods. The
  • Gen.containerOf[C[_],T]-methods have been kept as a convenience.

New in ScalaCheck 1.11.5 (Jul 29, 2014)

  • A minor release with just a few fixes since the last release.

New in ScalaCheck 1.11.4 (May 10, 2014)

  • A minor release with a few fixes and additions since the last release. The trait org.scalacheck.Commands has been deprecated since it will be removed and replaced with a completely new implementation in ScalaCheck 1.12.0.

New in ScalaCheck 1.11.0 (Nov 4, 2013)

  • The biggest change in this release of ScalaCheck is the generator
  • implementation that has been rewritten more or less from scratch. The new
  • implementation is smarter when it comes to test case simplification.
  • Previously, the test case simplification process had no knowledge about the
  • generator that produced the original value. This would lead to some confusion
  • since ScalaCheck could present a failing test case that couldn't have been
  • produced directly by the generator used. The new implementation lets the
  • shrinker take the generator boundaries into account when simplifying values. In
  • most cases this works transparantely without any assistance needed from the
  • user, but sometimes explicit boundaries must be assigned to the generator. This
  • is done with the standard Gen.suchThat method.
  • Apart from the new generator implementation, several new methods and
  • combinators have been added in several parts of the API. Some methods have been
  • renamed and some classes have been moved around to make the API more clear.
  • ScalaCheck 1.11.0 introduces API changes, but most users should hopefully only
  • need to change their code if they're using code that was deprecated in the
  • previous ScalaCheck release. However, recompilation is needed since ScalaCheck
  • 1.11.0 is not binary compatible with previous versions.
  • Support for Scala versions prior 2.9.3 has been dropped.
  • A new ScalaCheck web site has been launched at http://www.scalacheck.org. The
  • new site collects ScalaCheck documentation and downloads in an accessible way.

New in ScalaCheck 1.10.1 (Jul 30, 2013)

  • Minor additions and fixes has been made.
  • The code has been adapted to Scala 2.10
  • Specifications are written in Scala, in a DSL-like fashion using combinators from the ScalaCheck library.
  • Properties are tested automatically, with test data generated by ScalaCheck. Data generation can be precisely controlled, and generation of custom data types is simple to define.
  • Failing test cases are simplified automatically, which makes pin-pointing error causes easier.
  • Support for stateful testing of command sequences, and simplification of failing command sequences.
  • The ScalaCheck library has no dependencies other than the Scala runtime.
  • ScalaCheck is well integrated with ScalaTest, SBT and Specs.

New in ScalaCheck 1.5 (Mar 2, 2009)

  • CHANGED: The method Prop.property has been deprecated in favour of the more appropriately named Prop.forAll method. Prop.property will be removed in a future release of ScalaCheck.
  • ADDED: Prop.throws combinator which creates a property that holds if a specific exception is thrown during evaluation.
  • ADDED: Possible to run a Prop or Properties instance as an application, and give testing parameters on the command line.
  • FIXED: StdRand has been moved to package util.
  • CHANGED: Now possible to add several labels to a property.