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
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]
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]
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 year ago
Bumps github.com/onsi/ginkgo/v2 from 2.9.2 to 2.12.0.
Release notes
Sourced from github.com/onsi/ginkgo/v2's releases.
... (truncated)
Changelog
Sourced from github.com/onsi/ginkgo/v2's changelog.
... (truncated)
Commits
2d6991av2.12.005de518feat: allow MustPassRepeatedly decorator to be set at suite level (#1266)d696c7bBump golang.org/x/tools from 0.11.0 to 0.12.0 (#1253)d47bbc9Bump commonmarker from 0.23.9 to 0.23.10 in /docs (#1256)ce78ac9chore: update test matrix for Go 1.21 (#1255)0ba1a35Bump golang.org/x/net from 0.12.0 to 0.14.0 (#1251)0776d13Bump golang.org/x/sys from 0.10.0 to 0.11.0 (#1252)27c2f5dfix-errors-in-readme (#1244)8f2740aBump github.com/onsi/gomega from 1.27.8 to 1.27.10 (#1241)a0d57acBump golang.org/x/tools from 0.10.0 to 0.11.0 (#1235)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show