Hi Paulo Sergio,

just to add to Cristiano's suggested solution that the key is the
ability to include/exclude stories and organising stories in different
folders is an easy way to do this.  Another way could be to use some
naming convention, i.e. have stories to be included to start with "inc_"
or some other prefix which you would exclude by default in the
StoryFinder lookup.

Cheers

On 03/09/2010 21:43, Paulo Sérgio Medeiros wrote:
> Hi Cristiano,
>
> Yeah, just after sending the message I was thinking about alternatives
> such as organizing the project in a way that I could use the exclude
> and include the ones I want to be executed. 
>
> I'll try this way. It will probably do the job. If there are any
> impediments in this regard we talk again.
>
> By the way, I noticed that many of the people names of this list seems
> to be Portuguese/Brazilian. Are the jbehave developers from Portugal/
> Brazil? :-)
>
> cheers.
>
> On Fri, Sep 3, 2010 at 5:15 PM, Cristiano Gavião <[email protected]
> <mailto:[email protected]>> wrote:
>
>     hummm...  this will depend a little on which mode you choosed to
>     run your tests. take a look here:
>     http://jbehave.org/reference/stable/running-stories.html
>
>     but won't be easier to put the stories that you won't to get
>     executed (the internal ones) on a diferent folders from the ones
>     that you wanted to (the main ones)?
>
>     doing this, I think it's easy to include or exclude the stories
>     that you want or not... in any mode...
>
>     cheers
>
>     Cristiano
>
>     Paulo Sérgio Medeiros escreveu:
>
>         Hello,
>
>         I'm thinking in implementing a way, if it already does not
>         exist, to define what stories will run in a test trial.
>         In my case, I want to define that when a story is a dependency
>         (specified in a GivenStories) of another it should not be
>         executed "alone" (but just when it is called in the
>         GivenStories statement)
>
>         As far as I could understand (I haven't dug very deep in this
>         issue) the most effective way to do this is to implement
>         StoryPathResolver or maybe extend StoryRunner.
>
>         So, before I begin implementing this I was wishing to know
>         first if this functionality is already implemented in jbehave
>         or, if it's not, what is the best way to implement this.
>
>         Thanks in advance,
>         Paulo Sergio.
>
>
>
>
>
>     ---------------------------------------------------------------------
>     To unsubscribe from this list, please visit:
>
>       http://xircles.codehaus.org/manage_email
>
>
>

Reply via email to