Skip to content

Releases: onsi/ginkgo

v2.14.0

11 Jan 21:24

Choose a tag to compare

2.14.0

Features

You can now use GinkgoTB() when you need an instance of testing.TB to pass to a library.

Prior to this release table testing only supported generating individual Its for each test entry. DescribeTableSubtree extends table testing support to entire testing subtrees - under the hood DescrieTableSubtree generates a new container for each entry and invokes your function to fill our the container. See the docs to learn more.

Fixes

Maintenance

v2.13.2

29 Nov 03:52

Choose a tag to compare

2.13.2

Fixes

v2.13.1

10 Nov 15:55

Choose a tag to compare

2.13.1

Fixes

  • 1296 fix(precompiled test guite): exec bit check omitted on Windows (#1301) [26eea01]

Maintenance

  • Bump github.com/go-logr/logr from 1.2.4 to 1.3.0 (#1291) [7161a9d]
  • Bump golang.org/x/sys from 0.13.0 to 0.14.0 (#1295) [7fc7b10]
  • Bump golang.org/x/tools from 0.12.0 to 0.14.0 (#1282) [74bbd65]
  • Bump github.com/onsi/gomega from 1.27.10 to 1.29.0 (#1290) [9373633]
  • Bump golang.org/x/net in /integration/_fixtures/version_mismatch_fixture (#1286) [6e3cf65]

v2.13.0

09 Oct 12:31

Choose a tag to compare

2.13.0

Features

Add PreviewSpect() to enable programmatic preview access to the suite report (fixes #1225)

v2.12.1

19 Sep 19:50

Choose a tag to compare

2.12.1

Fixes

Maintenance

v2.12.0

23 Aug 23:07

Choose a tag to compare

2.12.0

Features

  • feat: allow MustPassRepeatedly decorator to be set at suite level (#1266) [05de518]

Fixes

Maintenance

Various chores/dependency bumps.

v2.11.0

16 Jun 17:12

Choose a tag to compare

2.11.0

In prior versions of Ginkgo specs the CLI filter flags (e.g. --focus, --label-filter) would override any programmatic focus. This behavior has proved surprising and confusing in at least the following ways:

  • users cannot combine programmatic filters and CLI filters to more efficiently select subsets of tests
  • CLI filters can override programmatic focus on CI systems resulting in an exit code of 0 despite the presence of (incorrectly!) committed focused specs.

Going forward Ginkgo will AND all programmatic and CLI filters. Moreover, the presence of any programmatic focused tests will always result in a non-zero exit code.

This change is technically a change in Ginkgo's external contract and may require some users to make changes to successfully adopt. Specifically: it's possible some users were intentionally using CLI filters to override programmatic focus. If this is you please open an issue so we can explore solutions to the underlying problem you are trying to solve.

Fixes

  • Programmatic focus is no longer overwrriten by CLI filters [d6bba86]

Maintenance

  • Bump github.com/onsi/gomega from 1.27.7 to 1.27.8 (#1218) [4a70a38]
  • Bump golang.org/x/sys from 0.8.0 to 0.9.0 (#1219) [97eda4d]

v2.10.0

07 Jun 04:12

Choose a tag to compare

2.10.0

Features

  • feat(ginkgo/generators): add --tags flag (#1216) [a782a77]
    adds a new --tags flag to ginkgo generate

Fixes

Maintenance

  • Bump golang.org/x/tools from 0.9.1 to 0.9.3 (#1215) [2b76a5e]

v2.9.7

31 May 03:37

Choose a tag to compare

2.9.7

Fixes

  • fix race when multiple defercleanups are called in goroutines [07fc3a0]

v2.9.6

31 May 01:40

Choose a tag to compare

2.9.6

Fixes

  • fix: create parent directory before report files (#1212) [0ac65de]

Maintenance

  • Bump github.com/onsi/gomega from 1.27.6 to 1.27.7 (#1202) [3e39231]