Releases: etorreborre/specs2
Releases · etorreborre/specs2
Maintenance release
Fixes
- core fixed the instantiation of specification objects with ScalaJS
ScalaJS 1.0 release
Maintenance release
Maintenance release
Fixes
- core #798 proper fix for possible regex match failures in
SpecificationFinderwhen trying to find specification class names
Maintenance release
Maintenance release
Fixes
- core #797 fixed the evaluation order for the List
Traverseinstance. This fixes the execution order for linked specifications - core prevent pattern match exceptions in the
SpecificationFinder
SPECS2-4.8.0
Maintenance release
Improvements
- guide better documentation for the
CommandLine.isSetmethod - core #772 allow to determine the duration before retry according the retry number (thanks to Cédric Chantepie)
- upgraded
sbtto1.3.3 - upgraded
scalacheckto1.14.2 - upgraded
mockito-coreto3.1.0
Fixes
- tests fixed some scalaz
Validationexamples - core fixed the case of
Array.empty must not be empty
SPECS2-4.7.1
SPECS2-4.7.0
Scala Native version!
Improvements
- runs on Scala 2.11 for Scala Native thanks to @lolgab
form,gwtandmarkdownare now crossprojects (@lolgab)- guide mention that
minTestsOkis equivalent tominSuccessfulTests(@jkleckner) - usual thanks to @xuwei-k for updating dependencies
Fixes
SPECS2-4.6.0
This version is compatible with both Scala 2.13 should be compatible with Dotty except for features using macros.
Improvements
- run on Scala 2.13 thanks to @SethTisue, @rossabaker
Fixes
- #751 fix for implicit resolution on Dotty thanks to @smarter
- #748 fixed a stack overflow with
Producer.emitSeq(could happen with large specifications) - #747 rethrow failures with a
notmatcher in mutable specs - fixed a comment on
SimpleTimerand added a return type - fixed one edge case with implicit resolution on Scala 2.13:
beSome(beLeft)(reported by @xuwei-k)
SPECS2-4.5.1
Maintenance version, with a change in the internal API which should not impact regular users.
The important fix is the one about the reported times which should be a lot more correct now.