Changelog

View Source

3.1

Enhancements

  • Added a new matcher be_error that can be used to verify a binding is an error tuple or ':error'

3.0

Enhancements

  • Suppress warnings from elixir 1.19 compiler
  • When a match fails, print the value of the variables instead of "expected 'my_var' to equal 'some_other_var'"

Breaking changes

  • Experimental : Custom Matcher interface has changed again, but it should be more stable now

v2.1

Enhancements

  • variables bound with pattern_match/1 are available for later assertions (see docs for pattern_match/1 for more info)

v2.0

Enhancements

  • Implementing custom matchers can be done using the CustomMatcher struct
  • expect/2 raises when provided incorrect arguments

Breaking changes

  • the previous tuple-based API for custom matchers is no longer supported

v1.0

This is our first v1.0 release, and it features a breaking change from the v0.1 version. In order to support negative assertions (eg: a value does not satisfy a matcher) we needed to rethink the interface between the matcher and expect. Doing so also enabled us to implement a fancy pattern_match/1 matcher.

Enhancements

  • our first v1 release !
  • support for asserting that a given value does not satisfy a matcher
  • added pattern_match/1 matcher that can verify a given value matches a pattern

Breaking changes

  • expect/1 can no longer be piped to matchers
  • all existing matchers have been rewritten to use a new interface with expect/1