-
Couldn't load subscription status.
- Fork 3
Update module github.com/onsi/ginkgo to v2 #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/github.com-onsi-ginkgo-2.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
41b1e68 to
3b7a380
Compare
29c168b to
36b1641
Compare
36b1641 to
e36b586
Compare
e36b586 to
08f9ea1
Compare
08f9ea1 to
488652d
Compare
488652d to
fc8386f
Compare
fc8386f to
54c5cb4
Compare
54c5cb4 to
03b42a2
Compare
03b42a2 to
c27649c
Compare
c27649c to
8f8b5c1
Compare
dcaa0d4 to
0a5b292
Compare
0a5b292 to
372e1b5
Compare
765214b to
3f8eff4
Compare
3f8eff4 to
70731cd
Compare
70731cd to
7a4b72e
Compare
807c73e to
b230c62
Compare
b230c62 to
f5e5287
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
f5e5287 to
10c7e46
Compare
687857a to
5efbe91
Compare
5efbe91 to
4510193
Compare
4510193 to
0677b89
Compare
77507cf to
a3a0f6e
Compare
a3a0f6e to
ebc7a84
Compare
ebc7a84 to
7137648
Compare
fa9b3aa to
1f82aea
Compare
0daed0d to
3a54e3f
Compare
3a54e3f to
fc0eb7f
Compare
fc0eb7f to
a2a9039
Compare
a2a9039 to
ba19b48
Compare
0274271 to
48aa7e2
Compare
48aa7e2 to
d2d3d0d
Compare
d2d3d0d to
749a726
Compare
749a726 to
57aaebe
Compare
57aaebe to
be721c1
Compare
be721c1 to
5a505a2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.14.1->v2.27.2Release Notes
onsi/ginkgo (github.com/onsi/ginkgo)
v2.27.2Compare Source
2.27.2
Fixes
a69113a]Maintenance
a99c6e0]f993df5]v2.27.1Compare Source
2.27.1
Fixes
606c1cb]a6463b3]v2.27.0Compare Source
2.27.0
Features
Transforming Nodes during Tree Construction
This release adds support for
NodeArgsTransformers that can be registered withAddTreeConstructionNodeArgsTransformer.These are called during the tree construction phase as nodes are constructed and can modify the node strings and decorators. This enables frameworks built on top of Ginkgo to modify Ginkgo nodes and enforce conventions.
Learn more here.
Spec Prioritization
A new
SpecPriority(int)decorator has been added. Ginkgo will honor priority when ordering specs, ensuring that higher priority specs start running before lower priority specsLearn more here.
Maintenance
1333dae]17ae63e]v2.26.0Compare Source
2.26.0
Features
Ginkgo can now generate json-formatted reports that are compatible with the
go testjson format. Useginkgo --gojson-report=report.go.json. This is not intended to be a replacement for Ginkgo's native json format which is more information rich and better models Ginkgo's test structure semantics.v2.25.3Compare Source
2.25.3
Fixes
f01aed1]v2.25.2Compare Source
2.25.2
Fixes
Add github output group for progress report content
Maintenance
Bump Gomega
v2.25.1Compare Source
2.25.1
Fixes
10866d3]2e42cff]v2.25.0Compare Source
2.25.0
AroundNodeThis release introduces a new decorator to support more complex spec setup usecases.
AroundNoderegisters a function that runs before each individual node. This is considered a more advanced decorator.Please read the docs for more information and some examples.
Allowed signatures:
AroundNode(func())-funcwill be called before the node is run.AroundNode(func(ctx context.Context) context.Context)-funccan wrap the passed in context and return a new one which will be passed on to the node.AroundNode(func(ctx context.Context, body func(ctx context.Context)))-ctxis the context for the node andbodyis a function that must be called to run the node. This gives you complete control over what runs before and after the node.Multiple
AroundNodedecorators can be applied to a single node and they will run in the order they are applied.Unlike setup nodes like
BeforeEachandDeferCleanup,AroundNodeis guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can callruntime.LockOSThread()in theAroundNodeto ensure that the node runs on a single thread).Since
AroundNodeallows you to modify the context you can also useAroundNodeto implement shared setup that attaches values to the context.If applied to a container,
AroundNodewill run before every node in the container. Including setup nodes likeBeforeEachandDeferCleanup.AroundNodecan also be applied toRunSpecsto run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.v2.24.0Compare Source
2.24.0
Features
Specs can now be decorated with (e.g.)
SemVerConstraint("2.1.0")andginkgo --sem-ver-filter="2.1.1"will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to @Icarus9913 for the PR.Fixes
3f5d379]. fixes #1582Maintenance
Numerous dependency bumps and documentation fixes
v2.23.4Compare Source
2.23.4
Prior to this release Ginkgo would compute the incorrect number of available CPUs when running with
-pin a linux container. Thanks to @emirot for the fix!Features
2b9c428]Fixes
1f59d07]Maintenance
2d134d5]v2.23.3Compare Source
2.23.3
Fixes
-as a standalone argument [cfcc1a5]feaf292]88e2282]v2.23.2Compare Source
2.23.2
🎉🎉🎉
At long last, some long-standing performance gaps between
ginkgoandgo testhave been resolved!Ginkgo operates by running
go test -cto generate test binaries, and then running those binaries. It turns out that the compilation step ofgo test -cis slower thango test's compilation step becausego teststrips out debug symbols (ldflags=-w) whereasgo test -cdoes not.Ginkgo now passes the appropriate
ldflagstogo test -cwhen running specs to strip out symbols. This is only done when it is safe to do so and symbols are preferred when profiling is enabled and whenginkgo buildis called explicitly.This, coupled, with the instructions for disabling XProtect on MacOS yields a much better performance experience with Ginkgo.
v2.23.1Compare Source
2.23.1
🚨 For users on MacOS 🚨
A long-standing Ginkgo performance issue on MacOS seems to be due to mac's antimalware XProtect. You can follow the instructions here to disable it in your terminal. Doing so sped up Ginkgo's own test suite from 1m8s to 47s.
Fixes
Ginkgo's CLI is now a bit clearer if you pass flags in incorrectly:
a0e52ff]b799d8d]This might cause existing CI builds to fail. If so then it's likely that your CI build was misconfigured and should be corrected. Open an issue if you need help.
v2.23.0Compare Source
2.23.0
Ginkgo 2.23.0 adds a handful of methods to
GinkgoT()to make it compatible with thetesting.TBinterface in Go 1.24.GinkgoT().Context(), in particular, is a useful shorthand for generating a new context that will clean itself up in aDeferCleanup(). This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.Features
37a511b]Fixes
7556a86]4df06c6]Maintenance
cbcf39a]9b261ff]00f19c8]e98a4df]60cc4e2]fea6f2d]31d7813]fc3bbd6]aee0d56]809a710]v2.22.2Compare Source
What's Changed
Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2
v2.22.1Compare Source
2.22.1
Fixes
Fix CSV encoding
aab3da6]c09df39]96a80fc]43dad69]Maintenance
c88c634]4df44bf]v2.22.0Compare Source
2.22.0
Features
0fcaa08]This allows serial tests to be filtered using the
label-filterMaintenance
Various doc fixes
v2.21.0Compare Source
2.21.0
Features
a69eb39]bcab9c8]Fixes
e548367]SpecsThatWillBeRunwithSpecsThatWillRun[
c2c4d3c]Maintenance
7e65a00]v2.20.2Compare Source
2.20.2
Require Go 1.22+
Maintenance
a671816]v2.20.1Compare Source
2.20.1
Fixes
d6f9640]v2.20.0Compare Source
2.20.0
Features
be5ab95]Maintenance
d303d14]7a50221]v2.19.1Compare Source
2.19.1
Fixes
63c8c30]ff41e27]Maintenance
76f4e0c]b69c00d]f097741]v2.19.0Compare Source
2.19.0
Features
Label Sets allow for more expressive and flexible label filtering.
v2.18.0Compare Source
2.18.0
Features
f010b65]d80eebe]Fixes
42013d6]Maintenance
fcf1fd7]8bb14fd]04bfad7]v2.17.3Compare Source
2.17.3
Fixes
ginkgo watchnow ignores hidden files [bde6e00]v2.17.2Compare Source
2.17.2
Fixes
32259c8]780e7a3]Maintenance
d91fe4e]8cb662e]3134422]eca81b4]760def8]4ce33f4]f2fcd97]fd622d2]5474a26]e6d1170]7f447b2]f15239a]v2.17.1Compare Source
2.17.1
Fixes
af0330d]v2.17.0Compare Source
2.17.0
Features
--github-outputfor nicer output in github actions [e8a2056]Maintenance
977bc6f]e297e7b]v2.16.0Compare Source
2.16.0
Features
Fixes
23f0cc5]cd418b7]Maintenance
2cebe8d]06de431]898cba9]17ae120]5a179ed]a1e6b69]d52951d]4471b2e]v2.15.0Compare Source
2.15.0
Features
8f3bd70]96e915c]Fixes
c245d09]dca77c8]dbaf18f]6f67a14]Maintenance
4fcd0b3]v2.14.0Compare Source
2.14.0
Features
You can now use
GinkgoTB()when you need an instance oftesting.TBto pass to a library.Prior to this release table testing only supported generating individual
Its for each test entry.DescribeTableSubtreeextends table testing support to entire testing subtrees - under the hoodDescrieTableSubtreegenerates 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.2Compare Source
2.13.2
Fixes
e2e81c8](*regexp.Regexp).MatchString(#1302) [3b2a2a7]v2.13.1Compare 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.0Compare Source
2.13.0
Features
Add PreviewSpect() to enable programmatic preview access to the suite report (fixes #1225)
v2.12.1Compare Source
2.12.1
Fixes
90d4846]Maintenance
555f543]d867b7d]v2.12.0Compare Source
2.12.0
Features
05de518]Fixes
27c2f5d]Maintenance
Various chores/dependency bumps.
v2.11.0Compare 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.0Compare Source
2.10.0
Features
a782a77]adds a new --tags flag to ginkgo generate
Fixes
548d78e]Maintenance
2b76a5e]v2.9.7Compare Source
2.9.7
Fixes
07fc3a0]v2.9.6Compare Source
2.9.6
Fixes
0ac65de]Maintenance
3e39231]v2.9.5Compare Source
2.9.5
Fixes
7fa0b6b]Maintenance
9f9d8b9]150e3f2]0013b1a]9e9e3e5]v2.9.4Compare 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.3Compare Source
2.9.3
Features
c0c77b6]Fixes
227c662]0de0e7c]Maintenance
8b925ab]e3795a4]b453793]73ed75b]0a2bc64]f41c557]8e423e5]v2.9.2Compare Source
2.9.2
Maintenance
3fcc5bf]6143ffe]v2.9.1Compare 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.0Compare 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.4Compare Source
2.8.4
Features
979fbc2]8432589]Fixes
a8bb39a]Maintenance
41b2a8a]7c4f583]v2.8.3Compare Source
2.8.3
Released to fix security issue in golang.org/x/net dependency
Maintenance
fc1a02e]0718693]v2.8.2Compare Source
2.8.2
Ginkgo now includes a
tools.gofile in the root directory of theginkgopackage. This should allow modules that simplygo get github.com/onsi/ginkgo/v2to also pull in the CLI dependencies. This obviates the need for consumers of Ginkgo to have their owntools.gofile and makes it simpler to ensure that the version of theginkgoCLI being used matches the version of the library. You can simply rungo run github.com/onsi/ginkgo/v2/ginkgoto run the version of the cli associated with your package go.mod.Maintenance
5767b0a]e1e9723]a588f60]v2.8.1Compare Source
2.8.1
Fixes
2d5075a]febbe38]Maintenance
11a4860]4890a62]a774638]3f233bd]f9b8649]6f8c042]833a75e]v2.8.0Compare 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.1Compare Source
2.7.1
Fixes
d2a1cb0]Maintenance
cafece6]eda66c2]ac5ccaa]eee6480]v2.7.0Compare 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.1Compare Source
2.6.1
Features
60240d1]Fixes
301f3e2]Maintenance
3643823]f9f856e]0d7087e]v2.6.0Compare Source
2.6.0
Features
ReportBeforeSuiteprovides access to the suite report before the suite begins.956e6d2]de44005]Fixes
2165648]v2.5.1Compare Source
2.5.1
Fixes
3ab38ae]55fc58d]8a14f1f]2669612]--progressdeprecation message (#1076) [b4b7edc]Maintenance
baea341]9646297]v2.5.0Compare 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
> Enterand< Exiteventsin 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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.