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]

2.13.0

Features

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

2.12.1

Fixes

• Print logr prefix if it exists (#1275) [90d4846]

Maintenance

• Bump actions/checkout from 3 to 4 (#1271) [555f543]
• Bump golang.org/x/sys from 0.11.0 to 0.12.0 (#1270) [d867b7d]

2.12.0

Features

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

Fixes

• fix-errors-in-readme (#1244) [27c2f5d]

Maintenance

Various chores/dependency bumps.

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]

2.10.0

Features

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

Fixes

• Fix broken link of MIGRATING_TO_V2.md (#1217) [548d78e]

Maintenance

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

2.9.7

Fixes

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

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]

2.9.5

Fixes

• ensure the correct deterministic sort order is produced when ordered specs are generated by a helper function [7fa0b6b]

Maintenance

• fix generators link (#1200) [9f9d8b9]
• Bump golang.org/x/tools from 0.8.0 to 0.9.1 (#1196) [150e3f2]
• fix spelling err in docs (#1199) [0013b1a]
• Bump golang.org/x/sys from 0.7.0 to 0.8.0 (#1193) [9e9e3e5]

2.9.4

Fixes

• fix hang with ginkgo -p (#1192) [15d4bdc] - this addresses a long standing issue related to Ginkgo hanging when a child process spawned by the test does not exit.

• fix: fail fast may cause Serial spec or cleanup Node interrupted (#1178) [8dea88b] - prior to this there was a small gap in which specs on other processes might start even if one process has tried to abort the suite.

Maintenance

• Document run order when multiple setup nodes are at the same nesting level [903be81]