I can see where the threading comes into play now, in the embedder we basically queue the stories in the StoryManager and then wait for it to finish running them and I understand why it does that.
In order to get around my issue, can I extend the StoryRunner and specify it somewhere in the config? I can't see anything obvious. cheers. On 9 March 2012 09:58, Graham Abell <[email protected]> wrote: > All, > > When I start running a test via embedder.runStoriesAsPaths(storyPaths) > runs the subsequent actions in a seperate thread. Is there a way to run > everything in the same thread? > > Our setup includes several ThreadLocal singletons which are instantiated > before embedder.runStoriesAsPaths() is called and therefore the subsequent > code can't access them as it stands. > > thanks, > Graham > >
