Great, I believe using a custom StoryLoader is the solution to this problem. Thank you for your quick reply!
On Sat, Mar 1, 2014 at 9:46 AM, Mauro Talevi <[email protected]>wrote: > Hi, > > JBehave story resources need not be written to disk. The story loading > is handled by the StoryLoader interface, which has different > implementations. > > You can implement your own story loader and configure it via the > Configuration.useStoryLoader(); > > Or you might be interested in the REST support that has been recently > added: > > http://jbehave.org/reference/stable/using-rest.html > > The main focus is still the I/O with the filesystem but you can pick and > choose the components you want to use a la carte. > > Cheers > > > On 28/02/2014 23:31, Brent Barker wrote: > >> Is it possible to run a story as a Story object, and not have to specify >> a path? >> >> Currently I'm retrieving stories from a online editor in the form of a >> json, and parsing that text into a story object via.. >> >> embedder.storyRunner().storyOfText(embedder.configuration(), >> storyText.toString(), "story name"); >> >> To run each story, I've had to execute them with.. >> >> embedder.storyRunner().run(embedder.configuration(), candidateSteps, >> story); >> >> I've edited the Embedder and StoryManager in an attempt to run them >> natively, and it seems to work. However, I was wondering if there was a >> better way to do this or if there was already something setup to do this? >> I'd rather not write the stories to disk. >> >> This stack overflow question gives some additional context to what I am >> trying to achieve >> http://stackoverflow.com/questions/16701341/run- >> jbehave-from-a-string-in-java >> >> Thanks in advance! >> -Brent >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
