Mauro, to your second point about the code completion/dynamic content in web-runner. That addition to web-runner would go a long way for my dept. Dev Eng and QA Eng has no trouble using jbehave but when I show it to a group of functional testers (whose domain knowledge is what jbehave can tap into) they have trouble cross referencing the steps into the story. My version of web-runner doesn't store/save the story text on the Run Story tab when I jump to the Find Steps tab to double check syntax. The web-runner is fabulous but that part can be discouraging for a functional tester building a story step by step. Dynamic step completion would solve all that. Thanks again, Seth
On Tuesday, December 6, 2011, Mauro Talevi <[email protected]> wrote: > Hi Louis, > thanks for article - has been added to the users' experiences page. > And thanks for feedback, always helpful. Could you please expand a bit on the error reporting features that your client would like to see improved? An example project would be most welcome. > > And yes, we are aware that better IDE editor integration would be useful - it's just that it takes time and it's not easy to do right ... we welcome people having the experience and willingness to help. What's crucial is that these IDE integrations need to complement (without repeating) the functionality and configuration of the core, i.e. provide an integration layer on top of the core. So far the attempts have fallen short of this main requirement. Also, supporting multiple IDEs (Eclipse, IDEA, etc) and everybody has its own way of doing things. UI experience is a difficult thing to get right. > > One thing we could do in the meantime is to enhance the Web Runner (which allows to run and find steps) to provide a wiki-style web dynamic interface to provide auto-completion and information about steps. It would be IDE-neutral and complement any IDE. > > Cheers > > On Mon Dec 5 15:43:53 2011, louis gueye wrote: >> >> 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 still < http://deepintojee.wordpress.com/2011/12/04/testing-error-handling-in-restful-application-with-jersey-and-jbehave/> write articles on jbehave. >> >> I'll keep you posted. >> >> Cheers. >> >> 2011/11/24 Mauro Talevi <[email protected] <mailto: [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: >> >> http://jira.codehaus.org/__browse/JBEHAVE-647 >> <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. >> >> http://deepintojee.wordpress. __com/2011/11/24/testing-rest-__content-negotiation-with-__jersey-and-jbehave/ >> < http://deepintojee.wordpress.com/2011/11/24/testing-rest-content-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 >> < https://github.com/jbehave/__jbehave-core/tree/master/__examples/trader-spring >> < https://github.com/jbehave/jbehave-core/tree/master/examples/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: >> >> http://xircles.codehaus.org/__manage_email >> <http://xircles.codehaus.org/manage_email> >> >> >> > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
