Onsi Fakhouri

hey there, sorry for the delay. Understood - in general while Ordered Containers exist and are fully supported my preference is to nudge users towards using smaller independent `It's where...

hey @felipe88alves - no strong reason. I've generally found the text in the contexts/describes/Its is enough to help understand what a `BeforeEach` is doing. And if there is need for...

Hey @astrieanna - this totally makes sense and is something I've done as well (usually as a `for` loop either around an `It` or in the body of an `It`)....

hey - this shipped in 2.0 and is documented [here](https://onsi.github.io/ginkgo/#ordered-containers).

Huh. I think the latest work on timelines in Ginkgo 2.5 also happens to solve for this. The JSON output format now includes SpecEvents which list the entry and exit...

hey @dhiller I don't think this is easily doable right now. A couple of options you can use today: 1. `ginkgo --fail-fast` will abort the suite after the first failure....

hey - sorry I was never able to circle back. Those `S`es each represent a single skipped spec. Let me know if there's anything about this behavior I can help...

Closing this out now that interruptible nodes and timeout decorators have been shipped.

I think I understand the issue here. relative paths don't work with `-r` because ginkgo changes the working directory to the test suite and then runs the `go test` command...

Sorry, I totally forgot about this. I'm going through and culling old/resolved issues but will keep this one around and try to get to it.