JBehave configuration classes

Description

I'm starting to find that there are multiple different things I might want to do, and the dependency injection mechanism isn't really working as well as I'd like for this.

It would be nice to produce a configuration that's easy to set up, and use that for everything. We could then have different ways of configuring JBehave, eg: environment-driven, settable, null (so you have to specify everything yourself), etc.

Going to have a play with this, driving it using the "broken scenarios only".

BTW, every time I get a "broken scenario" or "error output" story, I'm driving it by actually breaking a story. You won't see these broken stories checked into the build, but it's easy enough to replicate yourself!

Activity

Fixed

Details

Assignee

Reporter

Fix versions

Priority

Created July 24, 2008 at 9:59 AM
Updated May 22, 2015 at 8:37 AM
Resolved August 20, 2008 at 11:28 AM