Update module github.com/onsi/ginkgo to v2 #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.16.4
->v2.17.1
Release Notes
onsi/ginkgo (github.com/onsi/ginkgo)
v2.17.1
Compare Source
2.17.1
Fixes
af0330d
]v2.17.0
Compare Source
2.17.0
Features
--github-output
for nicer output in github actions [e8a2056
]Maintenance
977bc6f
]e297e7b
]v2.16.0
Compare Source
2.16.0
Features
Fixes
23f0cc5
]cd418b7
]Maintenance
2cebe8d
]06de431
]898cba9
]17ae120
]5a179ed
]a1e6b69
]d52951d
]4471b2e
]v2.15.0
Compare Source
2.15.0
Features
8f3bd70
]96e915c
]Fixes
c245d09
]dca77c8
]dbaf18f
]6f67a14
]Maintenance
4fcd0b3
]v2.14.0
Compare Source
2.14.0
Features
You can now use
GinkgoTB()
when you need an instance oftesting.TB
to pass to a library.Prior to this release table testing only supported generating individual
It
s for each test entry.DescribeTableSubtree
extends table testing support to entire testing subtrees - under the hoodDescrieTableSubtree
generates a new container for each entry and invokes your function to fill our the container. See the docs to learn more.65ec56d
]4a2c832
]92b6744
]Fixes
beb9507
]4ac3a13
]b2e5bc5
]Maintenance
465a8ec
]eab0e40
]fbf9724
]3ee80ee
]123e1d5
]558f6e0
]84ff7f3
]v2.13.2
Compare Source
2.13.2
Fixes
e2e81c8
](*regexp.Regexp).MatchString
(#1302) [3b2a2a7
]v2.13.1
Compare Source
2.13.1
Fixes
1296 fix(precompiled test guite): exec bit check omitted on Windows (#1301) [
26eea01
]Maintenance
7161a9d
]7fc7b10
]74bbd65
]9373633
]6e3cf65
]v2.13.0
Compare Source
2.13.0
Features
Add PreviewSpect() to enable programmatic preview access to the suite report (fixes #1225)
v2.12.1
Compare Source
2.12.1
Fixes
90d4846
]Maintenance
555f543
]d867b7d
]v2.12.0
Compare Source
2.12.0
Features
05de518
]Fixes
27c2f5d
]Maintenance
Various chores/dependency bumps.
v2.11.0
Compare Source
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: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
d6bba86
]Maintenance
4a70a38
]97eda4d
]v2.10.0
Compare Source
2.10.0
Features
a782a77
]adds a new --tags flag to ginkgo generate
Fixes
548d78e
]Maintenance
2b76a5e
]v2.9.7
Compare Source
2.9.7
Fixes
07fc3a0
]v2.9.6
Compare Source
2.9.6
Fixes
0ac65de
]Maintenance
3e39231
]v2.9.5
Compare Source
2.9.5
Fixes
7fa0b6b
]Maintenance
9f9d8b9
]150e3f2
]0013b1a
]9e9e3e5
]v2.9.4
Compare Source
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
903be81
]v2.9.3
Compare Source
2.9.3
Features
c0c77b6
]Fixes
227c662
]0de0e7c
]Maintenance
8b925ab
]e3795a4
]b453793
]73ed75b
]0a2bc64
]f41c557
]8e423e5
]v2.9.2
Compare Source
2.9.2
Maintenance
3fcc5bf
]6143ffe
]v2.9.1
Compare Source
2.9.1
Fixes
This release fixes a longstanding issue where
ginkgo -coverpkg=./...
would not work. This is now resolved and fixes #1161 and #99526ca1b5
]fc44c3b
]Maintenance
93de676
]v2.9.0
Compare Source
2.9.0
Features
AttachProgressReporter is an experimental feature that allows users to provide arbitrary information when a ProgressReport is requested [
28801fe
]GinkgoT() has been expanded to include several Ginkgo-specific methods [
2bd5a3b
]The intent is to enable the development of third-party libraries that integrate deeply with Ginkgo using
GinkgoT()
to access Ginkgo's functionality.v2.8.4
Compare Source
2.8.4
Features
979fbc2
]8432589
]Fixes
a8bb39a
]Maintenance
41b2a8a
]7c4f583
]v2.8.3
Compare Source
2.8.3
Released to fix security issue in golang.org/x/net dependency
Maintenance
fc1a02e
]0718693
]v2.8.2
Compare Source
2.8.2
Ginkgo now includes a
tools.go
file in the root directory of theginkgo
package. This should allow modules that simplygo get github.com/onsi/ginkgo/v2
to also pull in the CLI dependencies. This obviates the need for consumers of Ginkgo to have their owntools.go
file and makes it simpler to ensure that the version of theginkgo
CLI being used matches the version of the library. You can simply rungo run github.com/onsi/ginkgo/v2/ginkgo
to run the version of the cli associated with your package go.mod.Maintenance
5767b0a
]e1e9723
]a588f60
]v2.8.1
Compare Source
2.8.1
Fixes
2d5075a
]febbe38
]Maintenance
11a4860
]4890a62
]a774638
]3f233bd
]f9b8649
]6f8c042
]833a75e
]v2.8.0
Compare Source
2.8.0
Features
e19f556
]Modeled after
testing.T.Helper()
. Now, rather than write code like:you can stop tracking offsets (which makes nesting composing helpers nearly impossible) and simply write:
2f6597c
]You can now write code like this:
to programmatically check whether a given set of labels will match the configured
--label-filter
.Maintenance
ea4966e
]9dd275b
]14e7bdd
]v2.7.1
Compare Source
2.7.1
Fixes
d2a1cb0
]Maintenance
cafece6
]eda66c2
]ac5ccaa
]eee6480
]v2.7.0
Compare Source
2.7.0
Features
e0123ca
] - Ordered containers that are also decorated with ContinueOnFailure will not stop running specs after the first spec fails.7a2b242
]e6e3b98
]49fab7a
]Fixes
89dda20
]b0bd77b
]v2.6.1
Compare Source
2.6.1
Features
60240d1
]Fixes
301f3e2
]Maintenance
3643823
]f9f856e
]0d7087e
]v2.6.0
Compare Source
2.6.0
Features
ReportBeforeSuite
provides access to the suite report before the suite begins.956e6d2
]de44005
]Fixes
2165648
]v2.5.1
Compare Source
2.5.1
Fixes
3ab38ae
]55fc58d
]8a14f1f
]2669612
]--progress
deprecation message (#1076) [b4b7edc
]Maintenance
baea341
]9646297
]v2.5.0
Compare Source
2.5.0
Ginkgo output now includes a timeline-view of the spec
This commit changes Ginkgo's default output. Spec details are now
presented as a timeline that includes events that occur during the spec
lifecycle interleaved with any GinkgoWriter content. This makes is much easier
to understand the flow of a spec and where a given failure occurs.
The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags
and the SuppressProgressReporting decorator have all been deprecated. Instead
the existing -v and -vv flags better capture the level of verbosity to display. However,
a new --show-node-events flag is added to include node
> Enter
and< Exit
eventsin the spec timeline.
In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit
reports can be configured and generated using
GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)
Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that
was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format
to build tooling on top of as it has stronger guarantees to be stable from version to version.
Features
0f2fa27
]Fixes
c70867a
]Maintenance
bb3b4e2
]v2.4.0
Compare Source
2.4.0
Features
5e33c75
]bf78c28
]047c02f
]Fixes
1403d3c
]2105ba3
]be6b5b9
]Maintenance
8a2f483
]529c4e8
]da09146
]918040d
]2098e4d
]1d74122
]4442772
]v2.3.1
Compare Source
2.3.1
Fixes
Several users were invoking
ginkgo
by installing the latest version of the cli viago install github.com/onsi/ginkgo/v2/ginkgo@latest
. When 2.3.0 was released this resulted in an influx of issues as CI systems failed due to a change in the internal contract between the Ginkgo CLI and the Ginkgo library. Ginkgo only supports running the same version of the library as the cli (which is why both are packaged in the same repository).With this patch release, the ginkgo CLI can now identify a version mismatch and emit a helpful error message.
bc4ae2f
]2691dd8
]Maintenance
822a937
]v2.3.0
Compare Source
2.3.0
Interruptible Nodes and Timeouts
Ginkgo now supports per-node and per-spec timeouts on interruptible nodes. Check out the documentation for all the details but the gist is you can now write specs like this:
and have Ginkgo ensure that the node completes before the timeout elapses. If it does elapse, or if an external interrupt is received (e.g.
^C
) then Ginkgo will cancel the context and wait for the Grace Period for the node to exit before proceeding with any cleanup nodes associated with the spec. Thectx
provided by Ginkgo can also be passed down to Gomega'sEventually
to have all assertions within the node governed by a single deadline.Features
SpecContext
also provides a mechanism for third-party libraries to provide additional information when a Progress Report is generated. Gomega uses this to provide the current state of anEventually().WithContext()
assertion when a Progress Report is requested.a4c9865
]Fixes
92c88d5
]1be2427
]Maintenance
57c373c
]30526d5
]cf611c4
]b541bcb
]v2.2.0
Compare Source
2.2.0
Generate real-time Progress Reports [
f91377c
]Ginkgo can now generate Progress Reports to point users at the current running line of code (including a preview of the actual source code) and a best guess at the most relevant subroutines.
These Progress Reports allow users to debug stuck or slow tests without exiting the Ginkgo process. A Progress Report can be generated at any time by sending Ginkgo a
SIGINFO
(^T
on MacOS/BSD) orSIGUSR1
.In addition, the user can specify
--poll-progress-after
and--poll-progress-interval
to have Ginkgo start periodically emitting progress reports if a given node takes too long. These can be overriden/set on a per-node basis with thePollProgressAfter
andPollProgressInterval
decorators.Progress Reports are emitted to stdout, and also stored in the machine-redable report formats that Ginkgo supports.
Ginkgo also uses this progress reporting infrastructure under the hood when handling timeouts and interrupts. This yields much more focused, useful, and informative stack traces than previously.
Features
BeforeSuite
,AfterSuite
,SynchronizedBeforeSuite
,SynchronizedAfterSuite
, andReportAfterSuite
now support (the relevant subset of) decorators. These can be passed in after the callback functions that are usually passed into these nodes.As a result the signature of these methods has changed and now includes a trailing
args ...interface{}
. For most users simply using the DSL, this change is transparent. However if you were assigning one of these functions to a custom variable (or passing it around) then your code may need to change to reflect the new signature.Maintenance
0ffde58
]896bbb9
]6d3a90e
]v2.1.6
Compare Source
2.1.6
Fixes
SuppressProgressReporting
decorator to turn off --progress announcements for a given node [dfef62a
]7373214
]v2.1.5
Compare Source
2.1.5
Fixes
6ad7138
]CurrentSpecReport
andAddReportEntry
are thread-safe [817c09b
]3cd8b93
]5cf23e2
] - even when only one spec has failedb1864ad
]219cc00
]71ebb74
]143d208
]b69554f
]Maintenance
e5dfce4
]7ae91c4
]e87a85a
]bbefe12
]9327906
]f44af96
]ef336aa
]v2.1.4
Compare Source
Fixes
when
when usingWhen
(this behavior was in 1.x but unintentionally lost during the 2.0 rewrite) [efce903
]a7bd1fe
]0976569
]aae4480
]f779385
]v2.1.3
Compare Source
See https://onsi.github.io/ginkgo/MIGRATING_TO_V2 for details on V2.
Fixes
ff12cee
]v2.1.2
Compare Source
Fixes
ginkgo unfocus
[a612ff1
]8fbfa02
]v2.1.1
Compare Source
See https://onsi.github.io/ginkgo/MIGRATING_TO_V2 for details on V2.
Fixes
ec17e17
]v2.1.0
Compare Source
See https://onsi.github.io/ginkgo/MIGRATING_TO_V2 for details on V2.
2.1.0 is a minor release with a few tweaks:
90868e2
] More details here.6f8577e
]718542a
,ecb7098
,146654c
,a8f9913
,6bdffde
,03dcd7e
]v2.0.0
: Ginkgo v2.0.0Compare Source
Ginkgo v2.0.0 is a major new release of Ginkgo.
The changes to Ginkgo are substantial and wide-ranging, however care has been given to ensure that most users will experience a smooth migration from V1 to V2 with relatively little work. A combined changelog and migration guides is available here and the Ginkgo docs have been updated to capture the new functionality in V2.
v1.16.5
Compare Source
1.16.5
Ginkgo 2.0 now has a Release Candidate. 1.16.5 advertises the existence of the RC.
1.16.5 deprecates GinkgoParallelNode in favor of GinkgoParallelProcess
You can silence the RC advertisement by setting an
ACK_GINKG_RC=true
environment variable or creating a file in your home directory called.ack-ginkgo-rc
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.