Releases: etorreborre/specs2
Releases · etorreborre/specs2
specs2 SPECS2-4.0.3
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
SPECS2-4.0.2
Maintenance version
Improvements
- core better display of failure messages for sets
Fixes
- core fixed the reporting of times when using
sequential
orskipAll
- 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
specs2-tests SPECS2-4.0.1
Maintenance version
Fixes
- core fixed some possible deadlock when using an implicit
ExecutionEnv
SPECS2-4.0.0
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
andValidationMatchers
to that module - scalaz dropped the support for scalaz
7.0
Improvements
- introduced a
org.specs2.specification.Retries
trait extendingAroundEach
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 withsection
markers and allow it to be selected
withinclude
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
specs2-tests SPECS2-3.9.4
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
SPECS2-3.9.2
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
SPECS2-3.8.9
Maintenance version
Improvements
- project made the build TLS friendly
- core added a
batchedSized(n: Int)
(orunbatched
) argument to control how many examples are executed concurrently at once.
(the default isRuntime.getRuntime.availableProcessors
) - scalaz added documentation for scalaz.Task matchers #548 (thanks to Fabio Labella)
- scalaz added a
Matcher
to assert that aTask
can fail with a specificException
#546 (thanks to Fabio Labella)