George,
JBehave supports Maven and Ant as command-line tools to run stories, via
custom goals and tasks.
In addition, provided you've configured your project correctly, you can
use JUnit within an IDE. You can also run via JUnit in command-line,
if you choose, but it's up to you to
Hi Seth,
tracking these requirements:
http://jira.codehaus.org/browse/JBEHAVE-669
http://jira.codehaus.org/browse/JBEHAVE-670
Hope to make some inroad into them quite soon.
Cheers
On 06/12/2011 15:17, Seth Carter wrote:
Mauro, to your second point about the code completion/dynamic content
Hi all,
Just found and joined this group. Looks like a great resource for help
and sharing experiences:)
I joined as a result of a specific discussion we are having about
scenario steps, as we are about to take the leap into the jBehave world
and need to try and understand things a little
Mauro,
I'm sorry that JBehave has become a walled garden where people cannot
get answers to simple questions.
I took care of the dependencies. Having programmed in Java for over a
decade, I quite understand classpaths.
The example does not run the stories via JUnit, and I can't find
Good luck with Cucumber.
On 17/12/2011 18:27, George Dinwiddie wrote:
Mauro,
I'm sorry that JBehave has become a walled garden where people cannot
get answers to simple questions.
I took care of the dependencies. Having programmed in Java for over a
decade, I quite understand classpaths.
Oh, Cucumber works great. I often use Ruby Cucumber running under JRuby
to develop java code. That does require knowing a little Ruby, though.
Cucumber-JVM isn't quite fully baked, but seems to be coming along nicely.
I guess I've just become too accustomed to fast cycle times to run my
Christian,
Welcome!!
I've seen aliases used as a way to deal with plurals / singular forms of
statements.
They really are to help with readability. So never anything like 50 aliases -
that
would be a test-smell.
The goal is to have visibility into the regular expressions that are used in
