Just wanted to add that I've worked with Cucumber/Cuke4Duke on JRuby and the team eventually switched since debugging was a pain. Dealing with the stacktraces through JRuby was a big pain...just an FYI from one teams experience.
Brian ----- Original message ----- From: "louis gueye" <[email protected]> To: [email protected] Date: Mon, 5 Dec 2011 15:43:53 +0100 Subject: Re: [jbehave-user] new article on jbehave Hi everyone, I finally did have my demo on jbehave. Just for you to know, at my client's jbehave is in competition with cucumber. The team already had a cucumber demo and it was my turn to give them a jbehave demo. The purpose is to get rid of fitnesse. The same use case had to be implemented. We used jbehave without maven, directly in intellij editor because they wanted a quick feedback. What did work : - java/spring/junit integration What was missing : - information about the test completion : the test runner runs all stories and is complete. It's not ok for them as they want a per/scenario completion status. it may be available in the reports but sometimes the execution fails to generate the reports. - information about errors : again errors are well reported in reports but not always. Plus we could not find log informations. - syntax coloring in editor : none - auto-completion of steps/syntax coloring/implem to definition navigation in stories : none To summarize : no editor to easily write stories and avoid syntax error and steps duplication they felt a bit blind when something goes wrong not enough detailed reporting Any contribution to clarify/explain/improve/workaround the above points is more than welcome I'm a bit sad but I hope the java integration will lead them to choose jbehave. I'm not discouraged and I [1]still write articles on jbehave. I'll keep you posted. Cheers. 2011/11/24 Mauro Talevi <[2][email protected]> Louis, very nice article. I think we should start collecting this and other users' experience in a doc page for people to benefit from: [3]http://jira.codehaus.org/browse/JBEHAVE-647 Cheers On Thu Nov 24 17:28:32 2011, louis gueye wrote: Hi all, I just finished my last article about content negotiation with jersey and jbehave. [4]http://deepintojee.wordpress.com/2011/11/24/testing-rest-conte nt-negotiation-with-jersey-and-jbehave/ I really hope it'll help many to know about jbehave or to understand it better. I'm willing to write many more small/medium articles of that kind to help promote jbehave. I'm not a talented developer, at least I don't feel talented enough to contribute to code, but I can write articles and an like it. Go Jbehave ! For the jbehave part I was inspired by the trader-spring <[5]https://github.com/jbehave/jbehave-core/tree/master/exampl es/trader-spring> example which is quite complete. Feel free to read/suggest/correct/share as you wish. Good reading, Cheers. -------------------------------------------------------------- ------- To unsubscribe from this list, please visit: [6]http://xircles.codehaus.org/manage_email References 1. http://deepintojee.wordpress.com/2011/12/04/testing-error-handling-in-restful-application-with-jersey-and-jbehave/ 2. mailto:[email protected] 3. http://jira.codehaus.org/browse/JBEHAVE-647 4. http://deepintojee.wordpress.com/2011/11/24/testing-rest-content-negotiation-with-jersey-and-jbehave/ 5. https://github.com/jbehave/jbehave-core/tree/master/examples/trader-spring 6. http://xircles.codehaus.org/manage_email --- Brian Repko LearnThinkCode, Inc. http://www.learnthinkcode.com email: [email protected] phone: +1 612 229 6779
