George Blue

Hi @kiranSalunkhe29. I'm not familiar with blackduck, but I can't find any references to `[email protected]` in the latest Ginkgo (v2). I wonder if the issue is that blackduck is consuming...

I think this is the right direction, but there is an issue around timing. Go 1.19 is still in support, and many folks are on older versions. Although Ginkgo only...

Although I don't see it in the documentation, it looks like you can use decorators in table tests: https://github.com/onsi/ginkgo/blob/8b925abe6639e4bfd62b9defc35c5da41da08d6a/table_dsl.go#L102 I would expect something like this to work: ```go Entry("title", Label("label"),...

Hi @4CaDlqr2aU. I see that the error message contains `Service broker error`. This normally means that the error comes from the service broker. So the CF CLI has successfully sent...

For the case: ```go foo, err := Bar(42) Expect(err).NotTo(HaveOccured()) // boring boilerplate // here come the real assertions ``` Gomega will allow you do to this: ```go Expect(Bar(42)).To(Equal("the answer to...

@thediveo, I've definitely used the pattern of defining a [generic `must()` function](https://github.com/cloudfoundry/cloud-service-broker/blob/63fa456dd1cafc5665c2c09526c761eb4e85b993/integrationtest/integrationtest_suite_test.go#L72-L75) in tests, and reflected that I should not need to keep writing the same function: ```go func must[A...

Perhaps the thing to do would be to start by defining `Successfully()` and delaying writing `Successfully2()` until later? The documentation could tell you how to do it yourself, so users...

@onsi, in response to [this comment](https://github.com/onsi/gomega/issues/628#issuecomment-1410310152), it is possible for functions to have properties in Go as long as they are named types, and it's done in the [Go standard...

For context, `errors.As()` was supported in https://github.com/onsi/gomega/pull/359 and proved to be problematic so was removed in https://github.com/onsi/gomega/pull/375. It's worth being aware of that history before attempting anything new.

Most of the situations where I've seen this requirement it's because people want more data when the test fails, for example: ```go code, message := foo() Expect(code).To(BeZero()) //