Thanks @nogates - and cool use case you have going :)

I can't think of an alternative approach. My only hesitation is including ResetGlobals in the top-level Ginkgo DSL. I think, as an alternative, this could go in the extensions folder as a new standalone package that simply exposes ResetGlobals. We should think about what to call that package - any suggestions?

Hey @onsi ! Thanks for the quick reply :)

I can't think of an alternative approach. My only hesitation is including ResetGlobals in the top-level Ginkgo DSL. I think, as an alternative, this could go in the extensions folder as a new standalone package that simply exposes ResetGlobals.

Yeah, that could work! Happy to move it there!

We should think about what to call that package - any suggestions?

well, I think globals (as in globals.Reset()), is the most descriptive one... I can't think in any other name that would be more accurate and less generic 😬

well, I think globals (as in globals.Reset()), is the most descriptive one... I can't think in any other name that would be more accurate and less generic 😬

Fair enough - would you be up for adding documentation explaining the original use-case? Within the context of an actual test suite running globals.Reset() would be no bueno - so we want to make sure folks understand that this is intended for meta testing.

Fair enough - would you be up for adding documentation explaining the original use-case? Within the context of an actual test suite running globals.Reset() would be no bueno - so we want to make sure folks understand that this is intended for meta testing.

Definitely! I forced pushed the branch and moved the ResetGlobals to the extensions/globals#Reset package as discussed!

Also, I added a long description to the beginning of that package explaining what is the purpose of it, and I did emphasize this functionality is not intended for normal ginkgo setups.

Let me know if all of this makes sense! Thanks a lot for the time reviewing this @onsi ! 🙇

Great! lgtm!

Thank you!