The behaviour of the meta-info is actually meant to be very generic and user-definable, i.e. you'll be able to define your own tags to your liking.
The story has not been implemented yet, but OTOH I don't see as particularly tricky or difficult. It's been getting increasingly requested so it's likely to be the next one to get done. You may expect a beta later this month. Cheers On 04/10/2010 22:38, Tahir Raza wrote: > Thanks for the prompt reply Mauro! > > Here is what I see getting implemented: > > * A way to indicate the Author(s) of a scenario > * A way to indicate the Owner of a story > * A way to indicate the Creation Date of a scenario > * A way to indicate the Last Update Date of a scenario > * The injection phase of the scenario (eg. grooming, planning, > development...) > > > > So if I were to use these tags, correct me please if I am wrong, most > likely I am going to use the *injection *tag and use it according to > what I earlier asked? Or are we going to have a separate way to TAG > scenarios like I mention earlier. > > 2nd Question, when do you think 3.1 is getting released. Like Beta or > Stable, if you have an idea. > > Thanks! > > Tahir > > > On Mon, Oct 4, 2010 at 4:26 PM, Mauro Talevi > <[email protected] <mailto:[email protected]>> wrote: > > It's slated for next release (3.1): > http://jira.codehaus.org/browse/JBEHAVE-220 > > > On 04/10/2010 22:24, Tahir Raza wrote: >> >> >> >> Hello, >> >> We are following BDD in our projects and have been using >> Cucumber/Cuke4Duke stuff for past 3 months. >> >> We just started to implement JBehave and check its features. >> >> *My question is, do you guys know if we have some TAG features in >> JBehave, like we have it in Cucumber >> *eg: http://github.com/aslakhellesoy/cucumber/wiki/tags >> >> >> *...@billing* >> Feature: Verify billing >> >> >> >> >> @important >> Scenario: Missing product description >> ..... >> Scenario: Several products >> >> These tags can be defined Dynamically in the step definitions >> file rather than Java file. The particular Tagged Scenarios can >> be invoked from Maven rather than running all the scenarios. >> >> >> Do you know how we can achieve the same behavior in JBehave. >> >> Your response will be highly appreciated. >> -- >> >> Regards, >> Tahir Raza >> >> >> >> -- >> >> Regards, >> Tahir Raza > > > > > -- > > Regards, > Tahir Raza
