there may be a problem with the space in the parameter (it looks like
its trying to run a class "failed"), try with an underscore instead
Tags at scenario level should definitely work, if you put the Meta after
the Scenario: line
On 22.03.2012 17:30, rakesh mailgroups wrote:
Hi Mauro,
I tried your example by having:
Meta: @outcome failed
and then running the Junit test with -Dmeta.filter='+outcome failed'
(IntelliJ run configurations).
I got a stacktrace:
Exception in thread "main" java.lang.NoClassDefFoundError: failed'
So at the moment, the only thing thats works is hard coding in tags in
the Embedder and then putting tags in the Meta section. I could not get
the tag to picked up at the scenario level.
I looked through examples on GitHub, there are no tags at scenario level.
I don't use maven (I use Gradle) but I'm sure lots of people run JBehave
tests via the IDE right?
Rakesh
On Thu, Mar 22, 2012 at 2:09 PM, Mauro Talevi
<[email protected]
<mailto:[email protected]>> wrote:
Hi,
yes, you can filter meta tags both at scenario and story level.
Have a look at the threads examples, e.g.
mvn clean install -Dmeta.filter='+outcome failed'
will only pick up the scenario with
Meta: @outcome failed
If you want to specify the meta filter programmatically, use the
Embedder.useMetaFilters() method.
Cheers
On 22/03/2012 14:56, rakesh mailgroups wrote:
an update.
I tried overriding the Embedder in my super class like this:
@Override
public Embedder configuredEmbedder() {
super.configuredEmbedder().useMetaFilters(Arrays.asList("-skip"));
return super.configuredEmbedder();
}
Now this works as long as the @skip is in the meta section of the
story file. I was putting the tag at the scenario level.
Is the filtering on a per story level only? Thats not great, I'm
working on related scenarios in one story file and I want to tag
scenarios.
Rakesh
On Thu, Mar 22, 2012 at 12:19 PM, rakesh mailgroups
<[email protected]
<mailto:[email protected]>> wrote:
still struggling with this....
I've marked one (of the two scenarios in my file) with @foo
and now want to exclude it from being run.
I looked at the configurations for running a JUnit test in
Intellij and my options are:
1. pass jvm options
2. pass environment variables
I created an environment variable called 'meta.filter' and
gave it the value 'foo'.
I did the same as a jvm argument to (-Dmeta.filter=foo). I
even tried with @foo as the value.
Both scenarios always run.
Must be something basic I 'm doing wrong.
Btw, the configuration options for running are so bewildering,
I'm using an abstract superclass with the following code:
public abstract class AbstractStoryConfigurator extends
JUnitStory {
@Override
public Configuration configuration() {
return new MostUsefulConfiguration()
.useStoryLoader(new
LoadFromClasspath(this.getClass()))
.usePendingStepStrategy(new
PassingUponPendingStep())
.useStoryReporterBuilder(new
StoryReporterBuilder().withDefaultFormats().withFormats(Format.CONSOLE,
Format.HTML));
}
@Override
public List<CandidateSteps> candidateSteps() {
return new InstanceStepsFactory(configuration(), new
AcmeSteps(), new PrimeSteps()).createCandidateSteps();
}
}
I wanted to use the annotations but I got confused. At least
this current config sort of works!
Thanks
Rakesh
On Wed, Mar 21, 2012 at 2:36 PM, Alex Lehmann
<[email protected]
<mailto:[email protected]>> wrote:
You can use the metaFilters parameter in the
@UsingEmbedder annotation if you are using an annotated
runner or use the useMetaFilters method for Embedder to
set the meta filters from your source code, e.g. passing
-skip or -wip to disable the respective scenarios
On 21.03.2012 13 <tel:21.03.2012%2013>:07, rakesh
mailgroups wrote:
I'm using the default way of running tests by
basically letting Gradle
and my IDE think they are JUnit tests. How do I pass
in a meta tag to
filter on?
I use Intellij btw.
Thanks
Rakesh
On Tue, Mar 20, 2012 at 10:39 PM, louis gueye
<[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>
wrote:
Hi Rakesh,
I use 3 useful tags : @wip (work in progress),
@done (implemented
and validated by PO), @ready (ready to get implemented)
The @wip is the active tag by default used in dev mode.
When I want to push on distant repository I run
switch my @wip to
done and run @done stories to b sure I've broken
nothing
--
Cordialement/Regards,
Louis GUEYE
linkedin <http://fr.linkedin.com/in/louisgueye> | blog
<http://deepintojee.wordpress.com/> | twitter
<http://twitter.com/#%21/lgueye>
2012/3/16 Bill Ross
<[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>
What if you tag the one you're working on, and
select by tag?
Bill
rakesh mailgroups
<[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>
wrote:
> Hi,
>
> I tend to write my scenarios first and then go back
and try
and implement
> them one by one.
>
> Is there a way I can comment out all but one
scenario so I
can work on it
> in isolation?
>
> Thanks
>
> Rakesh
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
