Thanks Mauro for this clarification. I'll definitely write some stuff in French about JBehave once I become more proficient with it. Regards, Julien.
2013/2/17 Mauro Talevi <[email protected]> > Running stories as embeddables is simply a layer of abstraction above > that of running stories as paths. Ultimately, all stories are run as > paths. If you run them as embeddables it may save you some configuration, > e.g. when extending JUnitStories. > > There is no specific documentation at present on themes/streams, since the > meta info as generic and completely defined by the user. > > Some docs on story mapping: > http://jbehave.org/reference/stable/story-mapping.html > > Do note that mapping can surely be more developed as a subject. Feel free > to contribute ideas and thoughts. > > On 16/02/2013 18:00, Julien Martin wrote: > > Mauro, > > 1. When would one run stories as embeddables versus run stories as paths? > > 2. Can you please point me to relevant documentation about > themes/streams of work? > > Regards, > Julien. > > 2013/2/14 Mauro Talevi <[email protected]> > >> >> 1. Embeddables are Java classes that can group one or more story paths, >> e.g. JUnitStory or JUnitStories, and are responsible for their own >> execution (via their instance of Embedder) >> >> Paths are the story paths as specified and to be executed require an >> Embedder to be provided >> >> 2. Story mapping is an association between stories and meta >> information, that allows the identification of themes or streams of work. >> >> >> On 14 Feb 2013, at 15:16, Julien Martin <[email protected]> wrote: >> >> Hello, >> >> I am new to JBehave and still trying to grasp the basic concepts >> underlying the framework. >> >> 1. My first question is about running stories: can anyone please >> explain what "*running stories as embeddables*" and "*running stories >> as paths*" mean? I did read the documentation here: >> http://jbehave.org/reference/stable/running-stories.html but I would be >> grateful if someone rephrased it. >> >> 2. My second question is about the maven plugin: what does "*mapping >> stories*" mean? >> >> Regards, >> >> Julien. >> >> > >
