Skip to content

Releases: onsi/gomega

v1.20.2

31 Aug 14:10
Compare
Choose a tag to compare

1.20.2

Fixes

  • label specs that rely on remote access; bump timeout on short-circuit test to make it less flaky [35eeadf]
  • gexec: allow more headroom for SIGABRT-related unit tests (#581) [5b78f40]
  • Enable reading from a closed gbytes.Buffer (#575) [061fd26]

Maintenance

  • Bump github.com/onsi/ginkgo/v2 from 2.1.5 to 2.1.6 (#583) [55d895b]
  • Bump github.com/onsi/ginkgo/v2 from 2.1.4 to 2.1.5 (#582) [346de7c]

v1.20.1

26 Aug 19:45
Compare
Choose a tag to compare

1.20.1

Fixes

Maintenance

  • test: add new Go 1.19 to test matrix (#571) [40d7efe]
  • Bump tzinfo from 1.2.9 to 1.2.10 in /docs (#564) [5f26371]

v1.20.0

20 Jul 15:58
Compare
Choose a tag to compare

Features

  • New gleak experimental goroutine leak detection package! (#538) [85ba7bc]
  • New BeComparableTo matcher(#546) that uses gocmp to make comparisons [e77ea75]
  • New HaveExistingField matcher (#553) [fd130e1]
  • Document how to wrap Gomega (#539) [56714a4]

Fixes

Maintenance

  • Bump various dependencies:

1.19.0

Features

  • New HaveEach matcher to ensure that each and every element in an array, slice, or map satisfies the passed in matcher. (#523) [9fc2ae2] (#524) [c8ba582]
  • Users can now wrap the Gomega interface to implement custom behavior on each assertion. (#521) [1f2e714]
  • ContainElement now accepts an additional pointer argument. Elements that satisfy the matcher are stored in the pointer enabling developers to easily add subsequent, more detailed, assertions against the matching element. (#527) [1a4e27f]

Fixes

v1.19.0

25 Mar 19:12
Compare
Choose a tag to compare

Features

  • New HaveEach matcher to ensure that each and every element in an array, slice, or map satisfies the passed in matcher. (#523) [9fc2ae2] (#524) [c8ba582]
  • Users can now wrap the Gomega interface to implement custom behavior on each assertion. (#521) [1f2e714]
  • ContainElement now accepts an additional pointer argument. Elements that satisfy the matcher are stored in the pointer enabling developers to easily add subsequent, more detailed, assertions against the matching element. (#527) [1a4e27f]

Fixes

v1.18.1

27 Jan 19:11
Compare
Choose a tag to compare
  • add pointer support to HaveField matcher (#495) [79e41a3]

v1.18.0

22 Jan 18:32
Compare
Choose a tag to compare

Features

  • Docs now live on the master branch in the docs folder which will make for easier PRs. The docs also use Ginkgo 2.0's new docs html/css/js. [2570272]
  • New HaveValue matcher can handle actuals that are either values (in which case they are passed on unscathed) or pointers (in which case they are indirected). Docs here. (#485) [bdc087c]
  • Gmeasure has been declared GA [360db9d]

Fixes

  • Gomega now uses ioutil for Go 1.15 and lower (#492) - official support is only for the most recent two major versions of Go but this will unblock users who need to stay on older unsupported versions of Go. [c29c1c0]

Maintenace

  • Remove Travis workflow (#491) [72e6040]
  • Upgrade to Ginkgo 2.0.0 GA [f383637]
  • chore: fix description of HaveField matcher (#487) [2b4b2c0]
  • use tools.go to ensure Ginkgo cli dependencies are included [f58a52b]
  • remove dockerfile and simplify github actions to match ginkgo's actions [3f8160d]

v1.17.0

07 Nov 19:23
Compare
Choose a tag to compare

1.17.0

Features

  • Add HaveField matcher [3a26311]
  • add Error() assertions on the final error value of multi-return values (#480) [2f96943]
  • separate out offsets and timeouts (#478) [18a4723]
  • fix transformation error reporting (#479) [e001fab]
  • allow transform functions to report errors (#472) [bf93408]

Fixes

Stop using deprecated ioutil package (#467) [07f405d]

v1.16.0

20 Aug 12:50
Compare
Choose a tag to compare

Features

v1.15.0

05 Aug 19:36
Compare
Choose a tag to compare

1.15.0

Fixes

The previous version (1.14.0) introduced a change to allow Eventually and Consistently to support functions that make assertions. This was accomplished by overriding the global fail handler when running the callbacks passed to Eventually/Consistently in order to capture any resulting errors. Issue #457 uncovered a flaw with this approach: when multiple Eventuallys are running concurrently they race when overriding the singleton global fail handler.

1.15.0 resolves this by requiring users who want to make assertions in Eventually/Consistently call backs to explicitly pass in a function that takes a Gomega as an argument. The passed-in Gomega instance can be used to make assertions. Any failures will cause Eventually to retry the callback. This cleaner interface avoids the issue of swapping out globals but comes at the cost of changing the contract introduced in v1.14.0. As such 1.15.0 introduces a breaking change with respect to 1.14.0 - however we expect that adoption of this feature in 1.14.0 remains limited.

In addition, 1.15.0 cleans up some of Gomega's internals. Most users shouldn't notice any differences stemming from the refactoring that was made.

v1.14.0

07 Jul 14:33
Compare
Choose a tag to compare

1.14.0

Features

  • gmeasure.SamplingConfig now suppers a MinSamplingInterval [e94dbca]
  • Eventually and Consistently support functions that make assertions [2f04e6e]
    • Eventually and Consistently now allow their passed-in functions to make assertions.
      These assertions must pass or the function is considered to have failed and is retried.
    • Eventually and Consistently can now take functions with no return values. These implicitly return nil
      if they contain no failed assertion. Otherwise they return an error wrapping the first assertion failure. This allows
      these functions to be used with the Succeed() matcher.
    • Introduce InterceptGomegaFailure - an analogue to InterceptGomegaFailures - that captures the first assertion failure
      and halts execution in its passed-in callback.

Fixes

  • Call Verify GHTTPWithGomega receiver funcs (#454) [496e6fd]
  • Build a binary with an expected name (#446) [7356360]