Congratulations to the team on the release of 3.3.
I'm new to JBehave, and even to BDD. A Rubyesque colleague recently
showed me Cucumber, and while I love the concept and the execution, I
really want a Java equivalent because that's my team's first language
and it will open up many interesting pathways of development. And
besides, I'd like to be able to hack on it.
I looked at cuke4duke, but JBehave 'feels' a closer fit for our team.
That said, one thing cuke4duke has which JBehave seems not to is the
ability to auto-generate Java step definitions. Am I right? Is this
still missing from JBehave? I've seen JBEHAVE-148, btw, which is still
unresolved.
It's a killer feature, because it really gets you to that sweet spot
where you can 'write the code you would like to have' at the very top,
and let everything cascade down from that. I know step definitions are
really easy, but I can really see my team - who are BDD (even TDD!)
resistant - blowing this up into a big issue.
afaict, JBehave typically starts only in Java world, and only then looks
for matching text stories. Stories which match nothing are just
invisible. Ideally, I'd be able to use or naturally configure up
something which
- is told about the totality of story locations
- searches for matching Java implementations
- generates Java for missing story components, outputting to some
configured path
Better still, it would be great if there were something which put all
text stories and all Java step implementations into the mix, and helped
to make the difference between the two zero.
Jon
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
