|
View:
New views
10 Messages
—
Rating Filter:
Alert me
|
|
|
[ANN] CucumberNice vegetable, nice tool.
It's my reimplementation of the story runner, addressing several shortcomings of the current one. And I'm calling them features instead of stories now, because that is what they are. http://github.com/aslakhellesoy/cucumber/ (The home page) http://gojko.net/2008/08/06/cucumber-next-generation-ruby-bdd-tool/ (Thanks Gojko) Take a look - it's taking shape. Aslak _______________________________________________ rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] CucumberI have pushed some updates to the documentation. Especially Rails
instructions (which describe Cucumber generators) should be useful for some of you. Aslak On Thu, Aug 7, 2008 at 2:26 PM, aslak hellesoy <aslak.hellesoy@...> wrote: > Nice vegetable, nice tool. > > It's my reimplementation of the story runner, addressing several > shortcomings of the current one. And I'm calling them features instead > of stories now, because that is what they are. > > http://github.com/aslakhellesoy/cucumber/ (The home page) > http://gojko.net/2008/08/06/cucumber-next-generation-ruby-bdd-tool/ > (Thanks Gojko) > > Take a look - it's taking shape. > > Aslak > rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] CucumberAslak,
Thanks for the great demo of Cucumber at Agile 2008. dean On Fri, Aug 8, 2008 at 8:58 AM, aslak hellesoy <aslak.hellesoy@...> wrote: I have pushed some updates to the documentation. Especially Rails -- Dean Wampler http://www.objectmentor.com http://www.aspectprogramming.com http://aquarium.rubyforge.org http://www.contract4j.org _______________________________________________ rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] CucumberAslak,
Is it the intention to only be able to do one scenario per feature? If I add a second scenario, I get a syntax error. If so, how are you going to organize hundreds of features? In my existing stories I typically call it something like "Managing Widgets" and then put the scenarios for all features related to that idea within that singular story file.
-Jake On Fri, Aug 8, 2008 at 11:48 AM, Dean Wampler <deanwampler@...> wrote:
_______________________________________________ rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] CucumberOn Fri, Aug 8, 2008 at 12:37 PM, Jake Howerton <jake.howerton@...> wrote:
> Aslak, > Is it the intention to only be able to do one scenario per feature? If I > add a second scenario, I get a syntax error. No, you can have as many scenarios as you want, and in fact you're encouraged to. I fixed a parser bug yesterday. It was a little finnicky with whitespace. Try to get the latest code. If it still fails to parse, please send me the feature file and I'll fix any remaining parser bugs. > If so, how are you going to organize hundreds of features? In my existing > stories I typically call it something like "Managing Widgets" and then put > the scenarios for all features related to that idea within that singular > story file. You can use the new "FIT table" feature to have several similar scenarios with different values, or you can split them up in several files. Check out the examples to see the tables in action. Cheers, Aslak > -Jake > On Fri, Aug 8, 2008 at 11:48 AM, Dean Wampler <deanwampler@...> wrote: >> >> Aslak, >> Thanks for the great demo of Cucumber at Agile 2008. >> dean >> >> On Fri, Aug 8, 2008 at 8:58 AM, aslak hellesoy <aslak.hellesoy@...> >> wrote: >>> >>> I have pushed some updates to the documentation. Especially Rails >>> instructions (which describe Cucumber generators) should be useful for >>> some of you. >>> >>> Aslak >>> >>> On Thu, Aug 7, 2008 at 2:26 PM, aslak hellesoy <aslak.hellesoy@...> >>> wrote: >>> > Nice vegetable, nice tool. >>> > >>> > It's my reimplementation of the story runner, addressing several >>> > shortcomings of the current one. And I'm calling them features instead >>> > of stories now, because that is what they are. >>> > >>> > http://github.com/aslakhellesoy/cucumber/ (The home page) >>> > http://gojko.net/2008/08/06/cucumber-next-generation-ruby-bdd-tool/ >>> > (Thanks Gojko) >>> > >>> > Take a look - it's taking shape. >>> > >>> > Aslak >>> > >>> _______________________________________________ >>> rspec-devel mailing list >>> rspec-devel@... >>> http://rubyforge.org/mailman/listinfo/rspec-devel >> >> >> >> -- >> Dean Wampler >> http://www.objectmentor.com >> http://www.aspectprogramming.com >> http://aquarium.rubyforge.org >> http://www.contract4j.org >> >> _______________________________________________ >> rspec-devel mailing list >> rspec-devel@... >> http://rubyforge.org/mailman/listinfo/rspec-devel > > > _______________________________________________ > rspec-devel mailing list > rspec-devel@... > http://rubyforge.org/mailman/listinfo/rspec-devel > rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] Cucumber> You can use the new "FIT table" feature to have several similar > scenarios with different values, or you can split them up > in several files. Check out the examples to see the tables in action. > > Cheers, > Aslak > I must of missed the "FIT table" feature at my previous glances at cumber. That is awesome!! You have truly given me a reason to mess around with this at work now. ;) I'm curious on why you have changed 'Story' to 'Feature'. Have you found that more customers relate to that wording better, or what is the motivation? Thanks for all your work on this, Ben Mabey http://www.benmabey.com/ _______________________________________________ rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] CucumberYour newest changes fixed my parse errors. Thanks.
Jake On Fri, Aug 8, 2008 at 12:59 PM, aslak hellesoy <aslak.hellesoy@...> wrote:
_______________________________________________ rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] CucumberOn Fri, Aug 8, 2008 at 1:52 PM, Ben Mabey <ben@...> wrote:
> >> You can use the new "FIT table" feature to have several similar >> scenarios with different values, or you can split them up >> in several files. Check out the examples to see the tables in action. >> >> Cheers, >> Aslak >> > > > I must of missed the "FIT table" feature at my previous glances at cumber. > That is awesome!! You have truly given me a reason to mess around with > this at work now. ;) > > I'm curious on why you have changed 'Story' to 'Feature'. Have you found > that more customers relate to that wording better, or what is the > motivation? > A story is first and foremost a tool for planning. It represents a piece of valuable functionality and a future conversation about fleshing out the details. When they have moved through the Scrum/XP/Kanban board from the backlog to done done done, they are thrown away. At this time they have transmogrified into a running, tested feature - (or rather added to new or existing features). Software consists of (hopefully valuable) features - not stories. Stories are just temporary artifacts that feed the augmentation of features in the software. Let's say you have a backlog of 10 stories. Stuff people want to do. When the stories are implemented, what you have is perhaps 4 features, which have increased in scope over time. The features stick (in the code and in the Cucumber feature files). The stories are forgotten and that's ok. I hope this clarifies a bit what I mean. Aslak > Thanks for all your work on this, > > Ben Mabey > http://www.benmabey.com/ > > _______________________________________________ > rspec-devel mailing list > rspec-devel@... > http://rubyforge.org/mailman/listinfo/rspec-devel > rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] Cucumberaslak hellesoy wrote:
> Nice vegetable, nice tool. (Sorry, Fozzie, I didn't know those pickles were loaded!) Where do you want bugs reported? The first thing I noticed is that installing webrat as a gem isn't enough; you have to install it as a plugin, or the features that depend on it will fail. I'm new to webrat, but I *think* that shouldn't be the case, reading the docs.. Jay Levitt > > It's my reimplementation of the story runner, addressing several > shortcomings of the current one. And I'm calling them features instead > of stories now, because that is what they are. > > http://github.com/aslakhellesoy/cucumber/ (The home page) > http://gojko.net/2008/08/06/cucumber-next-generation-ruby-bdd-tool/ > (Thanks Gojko) > > Take a look - it's taking shape. > > Aslak > _______________________________________________ > rspec-devel mailing list > rspec-devel@... > http://rubyforge.org/mailman/listinfo/rspec-devel _______________________________________________ rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
|
|
Re: [ANN] CucumberJay Levitt wrote:
> aslak hellesoy wrote: >> Nice vegetable, nice tool. > > (Sorry, Fozzie, I didn't know those pickles were loaded!) > > Where do you want bugs reported? The first thing I noticed is that > installing webrat as a gem isn't enough; you have to install it as a > plugin, or the features that depend on it will fail. I'm new to > webrat, but I *think* that shouldn't be the case, reading the docs.. > and merb ones) for the same reason I keep versions of rspec and rspec-rails in my rails projects. So I think using it as a plugin/local gem is really the norm. -Ben _______________________________________________ rspec-devel mailing list rspec-devel@... http://rubyforge.org/mailman/listinfo/rspec-devel |
| Free embeddable forum powered by Nabble | Forum Help |