cats-effect-testing

User-Facing Pull Requests

• #390 – Updated Scala and Cats Effect versions (@djspiewak)
• #358 – Add assertions to assertThrows (@custommonkey)
• #377 – Cross-build for Native (@armanbilge)
• #360 – Replace serial scalatest ExecutionContext with global (@custommonkey)
• #370 – specs2 is published for Scala3 (@hamnis)
• #246 – assertion-for-exception-messages (@rtjfarrimond)

Special thanks to everyone!

The primary change in this release is the upgrade to Cats Effect 3.3.0, which brings with it some major changes within the cats-effect-testkit artifact. In particular, TestContext has been changed and TestControl has been introduced, the latter of which supersedes functionality previously partially provided by DeterministicIOTestSuite and similar. To that end, the direct TestContext integrations have been deprecated and will be removed in 2.0.0. It is recommended that users simply use TestControl directly with a conventional IO test suite.

User-Facing Pull Requests

• #234 – Updated to Cats Effect 3.3.0 (@djspiewak)
• #231 – Update specs2-core to 4.13.1 (@scala-steward)
• #226 – Convert ioRuntime to lazy val (@ex0ns)
• #212 – Update to Scala 3.1.0 (@scala-steward)
• #210 – Update Scala.js to 1.7.1 (@scala-steward)
• #208 – Update scalatest to 3.2.10 (@scala-steward)

The most significant change in this release comes in the form of the supporting artifacts. It appears that the core module, which contains functionality common to all test adapters, has been published under the org.typelevel::core artifact ID since 1.0. Since this has never been reported, we can only assume that no one is depending on this artifact directly (only indirectly via the test adapter modules), which is why we made the decision to rename it to cats-effect-testing-core without a breaking version bump.

We sincerely apologize for any inconvenience.

• #191 – Rename core artifact to cats-effect-testing-core (@armanbilge)
• #186 – Remove scalatest-scalacheck, link scalacheck-effect (@rossabaker)

Special thanks to both of you!

The primary feature of this release is correcting the fact that ScalaJS support previously… didn't exist at all! Due to a weird sbt bug and an inattentive eye (mine), ScalaJS support has been broken since 1.0. Meaning that, uh, this is the first release where it works.

• #180 – Fixed ScalaJS (@djspiewak)
• #173 – Add support for scalatest eventually by implementing Retrying typeclass (@skennedy)
• #162 – Add explicit support for timeout to UnsafeRun (@armanbilge)

• #158 – build: Scala 3 & dependencies (@ahjohannessen)
• #160 – Documentation updates and improvements (@LLCampos)

• Updated for Scala 3

• Added support for Scala 3.0.0-RC3
• Dropped support for Scala 3.0.0-RC2
• Updated Cats Effect to 2.5.0
• Updated ScalaTest to 3.2.6

• Added support for Scala 3.0.0-RC3
• Dropped support for Scala 3.0.0-RC2
• Updated Specs2 to 4.11.0
• Updated minitest to 2.9.5
• Updated Cats Effect to 3.1.0
• Updated µTest to 0.7.9

• Added support for Scala 3.0.0-RC2
• Dropped support for Scala 3.0.0-RC1
• Updated Specs2 to 4.10.6
• Updated Cats Effect to 3.0.1
• Updated ScalaTest to 3.2.6

• Updated to Cats Effect 3.0.0

• Updated Cats Effect to 3.0.0-RC3

This is the first release provided under the org.typelevel groupId!

• Updated to Cats Effect 3.0.0-RC2
• Added support for Scala 3.0.0-RC1
• Removed support for Scala 3.0.0-M3

• Added support for Scala 3.0.0-RC1
• Dropped support for Scala 3.0.0-M3

• Dropped support for Scala 3.0.0-M2
• Added support for Scala 3.0.0-M3
• Updated several dependencies to minor version bumps

• Updated to Cats Effect 3 (version 3.0.0-M5 at present)
• Added support for ScalaJS
• Rewrote Specs2 support to be fully asynchronous
• Removed scalatest-scalacheck support (for now)
• Removed µTest support due to ongoing release issues (the µTest artifacts are frequently released Java 11-only, which is problematic)
• Refactored the API to be more in line with what should be expected within the Cats Effect 3 framework
• Added UnsafeRun abstraction. This typeclass must be implemented for any datatype which is intended to be used with cats-effect-testing. At present, the only implementation is for IO, which also implies a dependency on Cats Effect core. This will be refactored before 1.0.0 goes final to allow for support for other datatypes.

• Updated Cats Effect to 2.3.0
• Updated minitest to 2.9.1
• Dropped support for Scala 3.0.0-M1 and added M2 (forced by µTest and minitest)
• Updated scalatest to 3.2.3
• Updated scalacheck to 1.15
• Updated the CatsResource mechanism in scalatest to be compatible with scalatest's async functionality (@Grogs)

This is the first release with full support for Dotty 0.27.0-RC1 and Scala 3.0.0-M1. Unfortunately, most of the supported test frameworks have still not released any recent-Dotty-compatible versions. At present, only the Specs2 module has been released, but it's likely that the others could be soon.

• Updated Specs2 to 4.10.5
• Updated ScalaCheck to 1.15.1
• Updated ScalaTestPlus-ScalaCheck to 3.2.2.0
• #54 – Make ExecutionContext available when mixin CatsIO trait (@tovbinm)
• Updated ScalaTest to 3.2.2
• Updated µTest to 0.7.5
• #84 – README improvements (@mcanlas)

• Updated µTest to 0.7.4
• Updated ScalaTest to 3.1.2
• Updated Specs2 to 4.10.0
• Support for Resource-based tests in ScalaTest (#72, @custommonkey)
• Support for Resource based tests in Specs2 (#69, @ChristopherDavenport)
• Abstracted testing style in ScalaTest to allow use with different styles (#43, @endertunc)

Thank you, everyone!

• Moved everything under cats.effect.testing top level package, to avoid import conflicts (thanks @Slakah!)
• ScalaTest 3.1.0 support
• Direct ScalaCheck property support (by @iRevive)

Continuing to flesh out our feature-set. Major changes:

• The Specs2 support is now generalized to any Effect, allowing convenient syntax for testing Monix Task and ZIO in addition to cats-effect's own IO. The CatsEffect trait represents the generalized version, while CatsIO is the mixin to use when testing with cats.effect.IO.
• ScalaTest support is here!

Remember that this is an 0.x release, so no particular compatibility guarantees are made with anything outside the 0.3.x major/minor pair. We'll be moving to stabilize things more in the future.