Published by onsi over 1 year ago
Published by onsi over 1 year ago
Published by onsi over 1 year ago
Published by onsi over 1 year ago
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.
Published by onsi over 1 year ago
Published by onsi over 1 year ago
Published by onsi over 1 year ago
This release fixes a longstanding issue where ginkgo -coverpkg=./...
would not work. This is now resolved and fixes #1161 and #995
Published by onsi over 1 year ago
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.
Published by onsi over 1 year ago
Published by blgm over 1 year ago
Released to fix security issue in golang.org/x/net dependency
Published by onsi over 1 year ago
Ginkgo now includes a tools.go
file in the root directory of the ginkgo
package. This should allow modules that simply go get github.com/onsi/ginkgo/v2
to also pull in the CLI dependencies. This obviates the need for consumers of Ginkgo to have their own tools.go
file and makes it simpler to ensure that the version of the ginkgo
CLI being used matches the version of the library. You can simply run go run github.com/onsi/ginkgo/v2/ginkgo
to run the version of the cli associated with your package go.mod.
Published by onsi over 1 year ago
Published by onsi over 1 year ago
Modeled after testing.T.Helper()
. Now, rather than write code like:
func helper(model Model) {
Expect(model).WithOffset(1).To(BeValid())
Expect(model.SerialNumber).WithOffset(1).To(MatchRegexp(/[a-f0-9]*/))
}
you can stop tracking offsets (which makes nesting composing helpers nearly impossible) and simply write:
func helper(model Model) {
GinkgoHelper()
Expect(model).To(BeValid())
Expect(model.SerialNumber).To(MatchRegexp(/[a-f0-9]*/))
}
You can now write code like this:
BeforeSuite(func() {
if Label("slow").MatchesLabelFilter(GinkgoLabelFilter()) {
// do slow setup
}
if Label("fast").MatchesLabelFilter(GinkgoLabelFilter()) {
// do fast setup
}
})
to programmatically check whether a given set of labels will match the configured --label-filter
.
Published by onsi over 1 year ago
Published by onsi almost 2 years ago
Published by onsi almost 2 years ago
Published by onsi almost 2 years ago
ReportBeforeSuite
provides access to the suite report before the suite begins.Published by onsi almost 2 years ago
--progress
deprecation message (#1076) [b4b7edc]Published by onsi almost 2 years ago
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
events
in 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.
Published by onsi about 2 years ago