Releases: scalatest/scalatest
3.1.3
ScalaTest 3.1.3 is a point release of ScalaTest that makes a few enhancements and fixes a few bugs, and supports Scala.js 1.1.1 and Dotty 0.26.
Changes included:
- Fix IllegalAccessException when comparing 2 instances of class has private fields. (#1859)
- Only expect non-filtered Async tests to be reported as completed in AsyncEngine, ParallelTestExecution and RandomTestOrder, which causes incorrect test count reported. (#1838)
- In SuiteSortingReporter, only remove suite reporter after the SuiteCompleted event is reported correctly. (#1850)
- Added support of asynchronous test in scalatest native build. (#1867)
- Improved Futures support by avoiding polling in Scala futures. (#1794)
Thanks to the contributors for the ScalaTest/Scalactic 3.2.1 release:
- Arnout Engelen (https://github.com/raboof)
- Tim Zhlobich (https://github.com/tim-zh)
- John Duffell (https://github.com/johnduffell)
- Guillaume Martres (https://github.com/smarter)
- Nicolas Stucki (https://github.com/nicolasstucki)
- Nguyen Hong Phuc (https://github.com/phucnh)
- Kirill A. Korinsky (https://github.com/catap)
- Bùi Việt Thành (https://github.com/giabao)
- Chua Chee Seng (https://github.com/cheeseng)
- Bill Venners (https://github.com/bvenners)
3.2.0
The release notes for ScalaTest/Scalactic 3.2.0 are here:
3.1.2
ScalaTest 3.1.2 is a minor release of ScalaTest that makes a few changes, and supports Scala.js 1.0.1 and Dotty 0.23.
Changes included:
- Be Scala 2.13.3 friendly (Symbol#toString change)
- Dotty 0.23.0 support.
- Built with Scala.js 1.0.1.
3.1.1
ScalaTest 3.1.1 is a minor release of ScalaTest that makes a few enhancements and fixes a few bugs, and supports Scala.js 1.0.0 and Dotty 0.22.
Changes included:
- Report unexpected value of Try in TryValues (#1738).
- Report unexpected value of Either in EitherValues. (#1738)
- Updates, especially to macros, to support Dotty 0.22.
- Updates to support Scala.js 1.0.0.
- Use cached thread pool unless explicit thread count given during parallel execution. (#1760)
- Fixed invalid property element in JUnit XML (#1767)
- Fixed stray timers in SuiteSortingReporter and TestSortingReporter. (#1774)
Thanks to the contributors for the ScalaTest/Scalactic 3.1.1 release:
- Robert Elliot (https://github.com/Mahoney)
- Nicolas Stucki (https://github.com/nicolasstucki)
- Fengyun Liu (https://github.com/liufengyun)
- Seth Tisue (https://github.com/SethTisue)
- Chua Chee Seng (https://github.com/cheeseng)
- Travis Brown (https://github.com/travisbrown)
- Lorenz Mende (https://github.com/LorenzMende)
- Bill Venners (https://github.com/bvenners)
3.1.0
The release notes for ScalaTest/Scalactic 3.1.0 are here:
3.1.0-RC3
release-3.1.0-RC3 tagging 3.1.0-RC3 release
3.0.8
Fixes
- Duplicate classes of JMock, JUnit, ScalaCheck, TestNG, EasyMock, and Selenium to org.scalatestplus.xxx packages, this fix problem for user using them from Java.
- Added root to the macros defined in TypeMatcherMacro.
- Changed Framework to flavour @WrapWith when it is available, consistent with behaviour of ScalaTestFramework and Runner.
- Fixed javascript error in report files generated by HtmlReporter.
Enhancements
- Make Prettifier to not depends on scala-xml classes, and removed scala-xml dependency from scalactic.
- Make StringOps in Prettifier to be compatible with Scala 2.13.0, all tests in AssertionsSpec now passes.
- Made Every's groupBy method to behave consistently in Scala 2.13.0.
- Use collection prefix from toString for ColCompatHelper's className implementation of Scala 2.13.0.
- Updated to use scala-js 0.6.28, 1.0.0-M3 and 1.0.0-M8.
Deprecations
- Deprecated org.scalatest.enablers.CheckerAsserting in favour of org.scalatestplus.scalacheck.CheckerAsserting.
3.0.7
This release has the same functionality as 3.0.6, and should be source compatible with 3.0.6, but unlike 3.0.6, is binary compatible with 3.0.5. Please see the release notes for 3.0.6 to find out the details of what the release contains. The goal with this release it to achieve binary compatibility with 3.0.5. Unfortunately although 3.0.6 should be source compatible with 3.0.5, it was not binary compatible.
3.0.7-RC1
This release has the same functionality as 3.0.6, and should be source compatible with 3.0.6, but unlike 3.0.6, is binary compatible with 3.0.5. Please see the release notes for 3.0.6 to find out the details of what the release contains. The goal with this release it to achieve binary compatibility with 3.0.5. Unfortunately although 3.0.6 should be source compatible with 3.0.5, it was not binary compatible.
3.0.6
Bug Fixes
- Fixed incorrect test count problem in scala-js starting 0.6.22.
- Fixed problem when partial unification is enabled with -Ypartial-unification.
- Enhanced TypeMatcherHelper to handle primitive types checking.
- Enhanced TypeMatcherHelper to handle AnyVal correctly.
Improvements
- Moved away from using octal escapes, as they are deprecated and will be removed in Scala 2.13.
- Wrap <script> sections of HtmlReporter in <![CDATA[]]>.
- Bumped up to use ScalaCheck 1.14.0.
- Bumped up to use scala-xml version 1.1.0.
- Bumped up to use scala-js version 0.6.26.
- Added support for Scala 2.13.0-M5.
Enhancements
- Added support of -T argument in SBT.
Deprecations
- Deprecated 'to' and 'until' method in Float and Double anyvals.
- Deprecated ScalaCheck related classes in org.scalatest.prop, moved the classes into org.scalatestplus.scalacheck.
- Deprecated classes in org.scalatest.easymock, moved the classes into org.scalatestplus.easymock
- Deprecated classes in org.scalatest.jmock, moved the classes into org.scalatestplus.jmock.
- Deprecated classes in org.scalatest.junit, moved the classes into org.scalatestplus.junit.
- Deprecated classes in org.scalatest.mockito, moved the classes into org.scalatestplus.mockito.
- Deprecated classes in org.scalatest.selenium, moved the classes into org.scalatestplus.selenium.
- Deprecated classes in org.scalatest.testng, moved the classes into org.scalatestplus.testng.
Autofix for ScalaTest 3.0
To help user to migrate from deprecated packages to new packages, we include a autofix tool that can help you to rename the package automatically.
If you're using the latest Scala 2.11 or 2.12, you can follow this guide to use autofix: