Onsi Fakhouri

hi there - in general i recommend against trying to orchestrate specs in parallel with goroutines the way you are trying to do. A lot of Ginkgo's assumptions are broken...

Hey there - there isn't formal support for this but you can do something like this: ```go It("should only rerun if a condition succeeds", FlakeAttempts(5), func() { if (CurrentSpecReport().NumAttempts >...

hi @AdarshdeepCheema I recommend reading this section of the documentation: https://onsi.github.io/ginkgo/#mental-model-ginkgo-assumes-specs-are-independent in short - Ginkgo does not guarantee order of specs. in fact it prefers to enable randomized spec orders...

hey @AdarshdeepCheema - there are many examples in the k8s community of folks using ginkgo to accomplish what you are aiming to do - including the k8s e2e suite itself...

hi - you can accomplish this today - simply define your code in a function in the external file and call that function in the It. I will not be...

i can reply in a bit more detail later but this section of the docs has some discussion of this: https://onsi.github.io/ginkgo/#dynamically-generating-specs your example will work but you will need to...

@AdarshdeepCheema I'd be happy to join a zoom call to have a face-to-face conversation about this if you would like. You can send me an e-mail at [email protected] and we...

In case there's interest, please take a look at the new proposal for managing shared resources and having finer-grained control over parallelism here: https://github.com/onsi/ginkgo/issues/1292

hey there i haven't played with it myself yet but my understanding from [the integration coverage docs](https://go.dev/testing/coverage/) and the latest [set of `go test` flags](https://pkg.go.dev/cmd/go/internal/test) is they you simply set...

what you’re describing is the default behavior. if you run: `ginkgo smoke component-1 component-2` it will stop after the first suite failes