specs2

Maintenance version, mostly with a JUnit enhancement

Enhancements

• junit #697 report failures when a specification fails to be created (Dávid István Bíró)

Fixes

• all #699 remove the procedure syntax (kenji yoshida)
• all #698 fixed a compile error with latest Scala 2.13.x (kenji yoshida)
• mock #690 display the proper failure message for a jmock failure

Maintenance version with an additional fix for possible stackoverflow exceptions on large specifications.

Fixes

• core #682 use constant stack running TimedFuture sequentially, too take constant stack while running examples in parallel (Edmund Noble)

Backport version

Fixes

• core #682 fixed a StackOverflow exception when running large specifications

Maintenance version with an important fix for possible stackoverflow exceptions on large specifications.

Improvements

• matcher #676 added matchers for cats.data.Validated (Isla Zhang)
• matcher #675 added "sized" matchers for cats.data.NonEmptyList (Keir Lawson)
• core #685 refactored the BlockDsl in mutable specifications to to allow the easy definition of other keywords than "can", "should",...

Fixes

• matcher #684 fixed the negation of a matcher in case of thrown expectations
• core #683 take constant stack while running examples in parallel (Edmund Noble)
• mock #679 fixed the use of the any[T] matcher

Code cleanup

• #677 removed redundant code (Keir Lawson)
• #674 removed references to deleted xor code (Keir Lawson)

Maintenance version, thanks Kenji Yoshida and others for the numerous small PRs!

Upgrades

• compiled with Scala 2.13.0-M4 and the new collections library
• upgraded sbt to 1.x
• upgraded scala-js to 0.6.23
• upgraded scalaz to 7.2.24

Fixes

• mock catch ExpectationError from JMock and make them failures #672
• matcher fixed the setting of messages with matchers throwing exceptions #655
• core fixed the 'humanName' method for anonymous classes on jdk >= 9 #659

Upgrade version

Upgrades

• scalacheck upgraded to ScalaCheck 1.14.0. It is now possible to visualize the seed used
  to generate a counter-example and reuse it to run a property (myProp.setSeed("xxx") or use scalacheck.seed xxx on the command line)

Improvements

• Use foldLeft instead of /: (#654) (thanks to @xuwei-k)

Fixes

• junit fixed an issue where List(1,2) must contain(===(2)) would fail with JUnitMatchers and a JUnit test class

Upgrade version

Upgrades

• mockito upgraded to Mockito 2.18.2, this is mostly to avoid a concurrency bug introduced by Mockito (#641).
• html the default options for pandoc are now compatible with pandoc 2.1.3 for markdown generation

Otherwise please refer to the 4.0.4 notes for the latest changes.

Maintenance version

Improvements

• mockito add anyFunction0 to the MockitoMatchers (#634) (thanks to @hmemcpy)
• mockito upgraded to Mockito 2.16.0 (#641)
• scala avoid procedure syntax (#647) (thanks to Kenji Yoshida)
• matcher-extra output better failure messages for Json matchers (#650)

Fixes

• various fixes to the test suite (#643, #644, #645) (thanks to @hmemcpy)
• core changed the fragment’s id to the hashcode of a fragment, rather than its location (#640). This fixes a
  description issue with JUnit when using Fragment.foreach (thanks to @hmemcpy)
• junit shutdown the execution environment after executing junit tests (#648)
• core fixed the visibility of AllExpectations.fragmentsFactory to allow mixing the trait with
  Before/After/Around Each (#651)

Maintenance version

Improvements

• build update and cleanup scala-parser-combinators dependency setting (#634) (thanks to Kenji Yoshida)
• build Adding support for sbt-crossproject (#621) (thanks to Matthew de Detrich)
• scala published for 2.13.0-M3
• core added a method to create specification links from specifications found with the SpecificationsFinder
• core skip the execution of examples if a step stops with a fatal error

Fixes

• matchers fixed a NPE with Json matchers when there are null values

Maintenance version

Improvements

• core better display of failure messages for sets

Fixes

• core fixed the reporting of times when using sequential or skipAll
• scalacheck fixed the reporting of scalacheck failures when using ThrownExpectations a duplicate "Failed after" message was reported on top of the actual message
• html remove ansi colors in Text when reported to html
• guide scalaz dependency is not mandatory since version 4.0.0 (thanks to kenji yoshida)
• core fixed ErrorOrOkOps.toErrorFullMessage (thanks to Shunsuke Otani)
• html specify charset when writing files (thanks to Andreas Flierl)
• html handle Windows file paths like Unix paths (thanks to Andreas Flierl)
• core simplify expressions by using Either.left (thanks to Shunsuke Otani)
• core avoid unnecessary conversions (thanks to João Costa)
• core fix multiple typos (thanks to João Costa)
• website fixed the link for the release notes
• website fixed the integration spec on the website

Maintenance version

Fixes

• core fixed some possible deadlock when using an implicit ExecutionEnv

Dependency-free version!

specs2-core is finally dependency-free and doesn't need to be built for various versions of Scalaz.
specs2-core is also now available for Scala.js

See the blog post for more information.

Changes

• project dropped the support for Scala 2.10
• core removed the dependency on Scalaz, there is now a specs2-fp module implementing a small amount of FP concepts
  to support the internal implementation of specs2 itself
• scalaz moved DisjunctionMatchers and ValidationMatchers to that module
• scalaz dropped the support for scalaz 7.0

Improvements

• introduced a org.specs2.specification.Retries trait extending AroundEach to retry each example
• introduced org.specs2.specification.core.OwnEnv/OwnExecutionEnv traits to isolate the execution environments of
  some specifications
• added addSections to "unit" specifications to enclose each block with section markers and allow it to be selected
  with include on the command line
• form display the actual value instead of the expected one for a Prop (this might be revisited in the future)

Fixes

• fixed the execution with stopOnXXX arguments for a sequential spec
• core the Result.foreach method must stop evaluating elements if there is an issue

Maintenance version (3.9.3 was incorrect)

Improvements

• core when checking for the equality of 2 sets of lines only run the edit distance difference on them if they are different.
  this improves build times

Fixes

• core set the minimum number of execution threads to 4 to avoid possible deadlocks on single core machines (cf some CI environments)
• core use the "user" execution environment to execute examples instead of specs2 own execution environment

Maintenance version

Improvements

• core display lines diffs when diffing sequences to better see the difference between 2 lists
• core better display of throwable diffs: first message diff then lines diffs for stacktraces

Fixes

• core catch failure exceptions in Executions. As a result some ScalaCheck properties were not failing #581
• core stop a specification execution if a step is a failure or an error
• forms fixed the reporting of forms (sbt + notifier + html)
• matcher-extra added implicit conversions for Double and BigDecimal to create json number matchers #582
• junit fixed the example prefixes in the xml report file #583

Maintenance version

Improvements

• project made the build TLS friendly
• core added a batchedSized(n: Int) (or unbatched) argument to control how many examples are executed concurrently at once.
  (the default is Runtime.getRuntime.availableProcessors)
• scalaz added documentation for scalaz.Task matchers #548 (thanks to Fabio Labella)
• scalaz added a Matcher to assert that a Task can fail with a specific Exception #546 (thanks to Fabio Labella)

Fixes

• core fixed retry in await helper #549 (thanks to Joao Azevedo)
• core removed all formatting for properties on ScalaCheck properties #545
• matcher array equality fix #541 (thanks to Noam Almog)