Hi Brian, thanks for sharing your presentation and feedback on JBehave. I found it quite an accurate representation of the features.
With reference to your "Cons": - jbehave-core jar bundles other libraries . Freemarker, Apache Commons collections, ioand lang This is an oversight and certainly not intended. I've created an issue to fix it: http://jira.codehaus.org/browse/JBEHAVE-273 -- Hamcrestlibrary issue with JUnit4 (in Eclipse) Not sure what your issue is - could you elaborate? -- IoCintegration shouldn't happen at scenario construction but rather as part of a TestRunner(like Spring Test framework does) . Not sure if this is part of JBehave3.0 or not . JUnitclasses are eagerly instantiated! There has indeed been a start of that in JB3. You'll find an example SpringTraderRunner that allow you to compose your dependencies via Spring's JUnit4 integration. Of course, the more detailed use cases the better support we can provide. Please feel free to suggest the way you'd like to see the integration working. Cheers On 13/04/2010 13:03, Brian Repko wrote: > JBehave team: > > Just wanted to let you know that I did a JBehave demo/presentation at > the Twin Cities (Minneapolis - St. Paul, MN, USA) Java Users Group. > You can find the code and presentation at http://www.learnthinkcode.com. > > I'd love feedback - and in particular, I'd be interested in reworking > the IoC integration - particularly Spring as what is there won't work > for large systems. In fact you might have to take some of the ideas > from the Spring Testing framework (common extension on both JUnit and > TestNG) in order to get JBehave to work well for large Spring systems. > > Thanks for a great tool and I look forward to sharing it and helping > to make it better!! > > Brian > --- > Brian Repko > LearnThinkCode, Inc. > email: brian.re...@learnthinkcode.com > phone: +1 612 229 6779
