The message below means that it has not found any story or scenario that matched the meta info.
Have you add it to your stories or scenarios? You'll need to have something like: Scenario: Meta: @UseCase My first use case In terms of configuration, it's better to keep the Configuration separate from the Embedder. Have a look at: http://git.codehaus.org/gitweb.cgi?p=jbehave-core.git;a=blob;f=examples/trader/src/main/java/org/jbehave/examples/trader/TraderStory.java In the constructor you can specify the meta filters on the Embedder. Or you may consider specifying the them via the Maven (or Ant, similarly). http://git.codehaus.org/gitweb.cgi?p=jbehave-core.git;a=blob;f=examples/trader/pom.xml Or even via annotations: http://git.codehaus.org/gitweb.cgi?p=jbehave-core.git;a=blob;f=examples/trader/src/main/java/org/jbehave/examples/trader/AnnotatedTraderEmbedder.java On 20/10/2010 21:21, Tahir Raza wrote: > I tried running like this: > > public Configuration configuration() { > Class<? extends Embeddable> embeddableClass = this.getClass(); > *Embedder embedder = new Embedder();* > ***embedder.useMetaFilters((asList("+UseCase *")));* > ***useEmbedder(embedder);* > return new MostUsefulConfiguration() > .useStoryLoader(new LoadFromClasspath(embeddableClass)) > .useStoryReporterBuilder( > new StoryReporterBuilder() > .withCodeLocation( > CodeLocations > .codeLocationFromClass(embeddableClass)) > .withDefaultFormats() > .withFormats(Format.CONSOLE, Format.TXT, > Format.HTML, Format.XML)); > } > > > but when i executed the story, it says the following in console, which > I cant comprehend. > > *Meta[properties={}] not allowed by filter '+UseCase *'* > > What am I doing wrong? > > > > On Wed, Oct 20, 2010 at 2:02 PM, Tahir Raza <[email protected] > <mailto:[email protected]>> wrote: > > Mauro, > > I am excited to use Tags!! Not exactly sure if I follow how to > configure it yet. Im still learning jbehave. > > Looking at code below, how do I configure the usage of tags. > > In our GlobalStories class that extends JUnitStories, we have the > following. (class is also attached) > / > / > /Thanks for the help man!/ > / > / > /@Override/ > ///public Configuration configuration() {/ > ///Class<? extends Embeddable> embeddableClass = this.getClass();/// > ///return new MostUsefulConfiguration()/ > ///.useStoryLoader(new LoadFromClasspath(embeddableClass))/ > ///.useStoryReporterBuilder(/ > ///new StoryReporterBuilder()/ > ///.withCodeLocation(/ > ///CodeLocations/ > ///.codeLocationFromClass(embeddableClass))/ > ///.withDefaultFormats()/ > ///.withFormats(Format.CONSOLE, Format.TXT,/ > ///Format.HTML, Format.XML));/ > ///}/ > > > > On Tue, Oct 19, 2010 at 7:28 AM, Mauro Talevi > <[email protected] <mailto:[email protected]>> > wrote: > > Tahir, > > 3.1-beta-1 now supports meta info, which can be use to filter > or map > stories: > > http://jbehave.org/reference/preview/meta-info.html > > As always, feedback is welcome. > > Cheers > > On 05/10/2010 15:58, Tahir Raza wrote: > > Thank you Mauro! > > > > On Mon, Oct 4, 2010 at 5:09 PM, Mauro Talevi > > <[email protected] <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>>> wrote: > > > > 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]> > >> <mailto:[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 > > > > > > > > > > -- > > > > Regards, > > Tahir Raza > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > > Regards, > Tahir Raza > > > > > -- > > Regards, > Tahir Raza
