Support configuration outside of suites

[Airblader]

#273 implemented a feature to make some things configurable, which is great. The problem is that we need to do this in every test suite such that it works regardless of which one we execute (during development). It would be great if this could be done in a more global way; some brainstorming:

1. Configuration through environment variables (probably not the greatest)
2. Configuration through a config file
3. Custom template for the Ginkgo CLI (<- not preferred since I personally don't use it to create new suites anyway).
4. ...?

[onsi]

I think config files will be the future for this sort of stuff in both ginkgo and gomega. But it's not a super high priority at the moment :/

[Airblader]

Totally understandable, just wanted to raise it for visibility. Thanks for the quick response!

Our solution for now is a shared setup function that we call from all suite definitions. It's not ideal since it relies on convention, but how the string comparisons are formatted is also not exactly a life-or-death thing.