Mauro, Thanks for the feedback - it actually was a great experience creating the example and I found it far more easy and far more effective than regular JUnit/mock type testing.
I saw the 2 tasks that you added to the JIRA, so thank you for that. The hamcrest issue is that in Eclipse, one can add a JUnit4 "container" which includes junit.jar and a hamcrest.jar which, being in Eclipse are connected via OSGi. When I used the JUnit4 container and hamcrest along with jbehave, I got really strange OSGi issues related to exported versions of the hamcrest jar. The workaround is not to use the JUnit4 container if you need hamcrest in your set of libraries. When I included them on the regular classpath, everything was fine. This seems to be more of a JUnit4 Eclipse container issue than a jbehave one - its just that in needing the hamcrest dependency, I hit this error. Its not your bug and there is nothing you can do about it. As for the Spring integration, I see alot of promise in marking Steps classes with @Component so that Spring will notice them and Autowire the dependencies - just makes them super easy to create. The problem is that creating the container in the Story/Scenario constructor doesn't work well with JUnit since JUnit constructs all the objects before running tests. The container needs to be created during the TestRunner but I wasn't sure if doing an addSteps call then would be too late. I'll take a look at the 3.0 stuff. Again - thanks for creating the task in JIRA. Again, being a big Spring fan, I'm interested in making the Spring integration top notch and I'll be happy to work on that. Thanks again for your work on JBehave - the room was packed (~40 people) and there is clearly interest in both JBehave and Cucumber. My goal is for a simple tool that does the job so I really want JBehave to be it. Thanks for presenting at Agile 2009 in Chicago - that is where I saw what you and Paul have created (I sat in the front and asked a bunch of questions). Brian ----- Original message ----- From: "Mauro Talevi" <[email protected]> To: [email protected] Date: Tue, 13 Apr 2010 23:27:22 +0100 Subject: Re: [jbehave-dev] JBehave 2.5 presentation and code samples 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: [1]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 [2]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: [3][email protected] phone: +1 612 229 6779 References 1. http://jira.codehaus.org/browse/JBEHAVE-273 2. http://www.learnthinkcode.com/ 3. mailto:[email protected] --- Brian Repko LearnThinkCode, Inc. email: [email protected] phone: +1 612 229 6779
