On Thu, Aug 21, 2008 at 6:08 PM, Joseph Wilk <[EMAIL PROTECTED]> wrote: > Hello, > > I've been looking through the cucumber documentation and have a couple > of questions. >
Hi, Sorry for the late reply, > I'm curious which of the disadvantages you list would be impossible/very > difficult in the classic story runner. I'm just trying to envisage if >From http://github.com/aslakhellesoy/cucumber/wikis - 10 means big effort, 1 small. Relatively. Your opinion may differ. 5: Hard to get started with. A special "all.rb" file must be written before it can be used. 3: No out of the box Rake support, which puts a lot of people off. 3: No i18n, so if you want to write stories in a different language than English you're out of luck. 8: Poor error reporting. No way to know on what line a plain text story failed during execution or parsing. 1: Limited colouring of output. 5: No simple way to execute only one scenario. 8: No command line tool to run stories. 2: No easy before or after hooks. 5: No highlighting of step parameters in the output 2: No detection of ambiguous step names > Cucumber and the classic story runner where to co-exist what would the > Cucumber plugin be able to do that the classic story runner could never I assume that by plugin you mean Rails plugin? (Cucumber is a standalone library that *may* be used as a Rails plugin). > realistically hope to achieve. > The Story runner could achieve this if someone put enough effort into it. That would have to be someone other than me, because I don't have the time (or desire) to do it. Let's say it's up for grabs. > Also looking at one of your disadvantages: > * 'Limited colouring of output' > I've been playing around with patches here and there to improve the > colour of the classic story runner formatters. Do you still see > limitations in this as it is in edge? > That's one of the easiest things to fix, and also one of the smallest disadvantages IMO. > My final question is about the Rspec book. I've no idea when this will > be released or what pressures there are on publish deadlines. How much > would this effect a move to Cucumber (avoiding having redundant story > examples in the book when we all use Cucumber)? > Regarding the book - we haven't decided whether or not to cover Cucumber. In any case, *writing* stories/features for the Story runner will be almost identical to Cucumber features. On Tuesday I ported one of our projects at work over to Cucumber. Over 1000 steps. I ended up having to change almost nothing in the text or step defs (except for resolving some duplicates and ambiguities that Cucumber complains about where RSR says nothing). I have written up what I did and will post it to the Cucumber wiki next week when I have some time to proofread it. Cheers, Aslak > Thanks, > -- > Joseph Wilk > http://www.joesniff.co.uk > aslak hellesoy wrote: >> On Wed, Aug 20, 2008 at 6:24 PM, Ben Mabey <[EMAIL PROTECTED]> wrote: >>>> * How to use without Rails >>> wiki be better? >>> >> >> Good idea, I have moved the README.textile to >> http://github.com/aslakhellesoy/cucumber/wikis/home >> >> Everyone here is welcome to edit it. If you have concrete experience >> (or wishes) about how to migrate existing stories to Cucumber this >> would be the place to do it. >> >> Aslak > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
