Hi Mauro, Thanks for replying, but I am afraid I did not understand your response.
My aim is to have one Scenario class, which can pick up every *.scenario file from a directory, run them against a Step class I have. This would let me add more .scenario files, expanding on the behavior (after development, but lets ignore that for now) of the system. My intention is to use the .scenario files as an "executable specification" of the system. Please post a skeleton example of the Scenario class if this can be done. Thanks, Binil On Fri, Jan 23, 2009 at 4:05 AM, Mauro Talevi <[email protected]>wrote: > Hi Binil, > > simply declare your Java Scenario class (that maps to the .scenario text > file) to use the same Steps class that you've implemented to map your steps > to Java methods. > > Easy as that. > > Cheers > > > Binil Thomas wrote: > >> Hi all, >> >> I have tried out jBehave in some smaller personal projects; now I am >> considering describing the expected functionality of a subsystem I am >> developing at work using jBehave. The advantage I see with jBehave is that I >> can describe the behavior of the system under various scenarios in clear >> plain text files. >> >> From my understanding of jBehave, the actual work of converting this text >> describtion into a "test" is done in the Steps class. The Scenario class >> associates a text file with a Step implementation. I would like my scenarios >> to be in individual .scenario text files. All the examples I have seen so >> far have one Scenario implementation for one .scenario file. Since all the >> Scenario class seems to be doing is to associate a .scenario file to a Step >> class, is there a way to write just one Scenario class to handle multiple >> .scenario files? >> >> Thanks, >> Binil >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
