We definitely want to streamline this a bit, I don't like the idea of having two methods doing similar things. I also don't like the idea of not being able to set the seed in the configuration. There are extension libraries that may want to, or might make use of this, so we should be setting the seed before all hooks run, before each spec. I think we should document how this happens, and tell people we expect them not to use code in the configuration that depends on a configured randomisation, or they should do it themselves, if they have setup dependencies which rely on the seed, they can move them to hooks.

One thing thats occured to me however... if we have code depending on seeded randomisation in before/after all hooks. How to we cope with that? As the seed will be reset before each example (to be predictable) but it means the first spec's sequence will either be identical to that of the all block, or be tainted by that all block.