Well, I can't follow your need.
this kind of pre-run configuration as loading default data, starting up
application server, setting up database connections, etc are normally done
using GivenStories (http://jbehave.org/reference/stable/given-stories.html)
or even Given steps...
this way you can cre
Configuration is currently split between embedder and steps. I most
implementation it is likely that steps need some general configuration… in my
case I am loading some default values from properties files, etc… it would be
nice to centralize all environment configuration in the embedder since i
In other words, there is an Inversion of Control between the runner and the
steps classes. The steps classes are agnostic of the runner.
Why do you feel the need to have them talk?
On 27 Jun 2013, at 16:23, Cristiano Gavião wrote:
> there is no preferred or correct way to do that... you can
there is no preferred or correct way to do that... you can't...
AnnotatedPathRunner was created to setup the Embedder that will run your
stories...
the configuration of your environment (the system under test) should be
done in your steps classes...
2013/6/27 Luigi Suardi
> I am using Annota
You can't.
On 27 Jun 2013, at 15:59, Luigi Suardi wrote:
> I am using AnnotatedPathRunner based configuration together with a standalone
> POJO step class.
>
> I would like to initialize all my environment configuration in the
> AnnotatedPathRunner and then access it from the steps class.
>
I am using AnnotatedPathRunner based configuration together with a standalone
POJO step class.
I would like to initialize all my environment configuration in the
AnnotatedPathRunner and then access it from the steps class.
What is the preferred/correct way to access the AnnotatedPathRunner from
I have found the problem… the AnnotatedPathRunner example was setting a custom
pattern prefix:
public static class MyRegexPrefixCapturingPatternParser extends
RegexPrefixCapturingPatternParser {
public MyRegexPrefixCapturingPatternParser() {
super("%");
}
}
A
This fixed it.
Thank you!
Luigi
From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
Sent: Wednesday, June 26, 2013 8:17 PM
To: user@jbehave.codehaus.org
Subject: Re: [jbehave-user] source build error
Looks like a corrupt file, delete its dir and build again.
On 26 Jun 2013, at 18:28, Lui
