Skip to content

Releases: disneystreaming/weaver-test

v0.8.4 : bug fixes

25 Jan 10:21
0643148
Compare
Choose a tag to compare

Bug fixes :

  • Fixed a bug that would lead tests to freeze upon failed IOs in Javascript : #725
  • Fixed a bug that would prevent source-location macro expansion when using mdoc : #702

Misc

Version updates

New Contributors

Full Changelog: v0.8.3...v0.8.4

v0.8.3: configurable stack-trace lengths

14 Apr 16:20
3da8ac3
Compare
Choose a tag to compare
  • Adds an environment-variable-driven mechanism to configure the minimum value for how much of a stack-trace is rendered when a test fails due to an exception.
  • Increases the default size of reported stack-traces from 10 frames to 50.
  • Adds documentation on usage in the context of scala-cli

What's Changed

New Contributors

Full Changelog: v0.8.2...v0.8.3

v0.8.2: `whenSuccess` combinator

24 Mar 08:11
b03d821
Compare
Choose a tag to compare
  • adds a whenSuccess combinator, see #615
  • more faithful fail-fast in scalacheck, see #631

What's Changed

New Contributors

Full Changelog: v0.8.1...v0.8.2

v0.8.1 : `.only` and `.ignore` improvements

20 Nov 09:17
734ae54
Compare
Choose a tag to compare
  • Tests tagged with .only will now fail in CI environments (checked via the presence of the CI env var)
  • Fixes a bug where the .ignore tag would have no effect in pure tests

What's Changed

Full Changelog: v0.8.0...v0.8.1

v0.8.0 : Scala-native support, dropping a number of things

16 Sep 13:35
850a8a6
Compare
Choose a tag to compare

This release is the first of the 0.8.0x lineage. It is not binary-compatible with previous versions, but it should be source compatible for the most part, unless you use one of the modules we're dropping.

This is a difficult release for us to put out because we know we'll be disappointing some people. We apologise for the inconvenience, and wish good luck to the people who have been using the modules in question. Feel free to copy/paste the code we're dropping.

Dropping non-CE effect types.

Head over there to read the why, but the tl;dr is maintenance burden. We are committing to keeping the core of weaver effect-agnostic, so if you want Monix, MonixBIO, or ZIO support revived, it is entirely possible (as long as these have CE3 integration).

Dropping CE2

We are effectively dropping CE2 support. We will keep accepting bug fixes (and helping out) on the 0.6.x lineage, but we won't be adding any new feature.

Dropping specs2

The specs2 integration was never perfect, due to reliance over implicit conversions that were created a lot of edge cases. People wanting to test effect-code with specs2 semantics should probably use cats-effect-testing, or come up with their own mechanism (or copy the old one in userland).

Scala Native

First good news of this release I suppose, weaver now works in Scala-Native, hurray 🎉 .

Static ignore

Another good piece of news : tests can now be ignored via the .ignore method on test names :

test("foo".ignore){
    IO(???) 
}

Thanks to @callado4 for the contribution !

What's Changed

New Contributors

Full Changelog: v0.6.15...v0.8.0

v0.6.15 : fix race condition in DisciplineFSuite

09 Aug 16:44
db11788
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.6.14...v0.6.15

v0.6.14: effect-able Discipline trait

29 Jul 10:31
dbca1d3
Compare
Choose a tag to compare

Adds a DisciplineF trait that allows to run context-aware laws (for instance, laws that depend on the presence of a database connection). Courtesy of @bwiercinski.

What's Changed

Full Changelog: v0.6.13...v0.6.14

v0.6.13 : deterministic Scalacheck properties

29 Jun 08:45
eb7a469
Compare
Choose a tag to compare

Highlights :

Changed the Scalacheck integration to increase determinism : previously, forall properties would be executed in parallel in a way that wouldn't conserve order, which lead runs originating from the same seed to exhibit different results. Now, the properties are still executed in parallel, but the processing of their outcomes respects the initial ordering.

This implies that, provided the properties do not depend on state of the outside world that might be subject to change (like, reading from a database record that could change for an external reason), the likelihood of having reproducible results is drastically increased. In particular, it means you can have fully deterministic unit tests, which wasn't the case before.

There is a little cost in terms of efficiency that should not be noticeable in most cases.

Kudos to @ollyw for the improvement !

What's Changed

Full Changelog: v0.6.12...v0.6.13

v0.6.12: improvements for ZIO suites

23 May 08:42
4e776a7
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.6.11...v0.6.12

v0.6.11 : Allows resource startup timeout to be configured

01 Mar 11:44
d3c11c2
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.6.10...v0.6.11