[rspec-users] workflow: user => stories/features => spec => code => user

Hi, I am still trying to learn how to effectively use BDD. I would like to know if there is a typical BDD workflow or if it is really just a question of personal preference. So far I see the following steps being fairly common: 1. talk with user to establish a few stories and features 2. write p

Re: [rspec-users] webrat the way to go?

Thank you all for your responses. This has been really helpful! Matt Wynne wrote: > I would expect to waste some time splashing around though, yup. I think I am going to have to book a "day off" next week and just dive into it all: lots of reading and lots of practice. Thanks again, Paul ___

Re: [rspec-users] [ANN] Cucumber Textmate Bundle

Jay Levitt wrote: > Ben Mabey wrote: > >> You can get it here: >> http://github.com/bmabey/cucumber-tmbundle/ > > This is probably blindingly obvious to anyone who's ever installed a > Textmate bundle from github before (i.e. not me), but you have to > rename cucumber-tmbundle to cucumber.tmbundle

Re: [rspec-users] [ANN] Cucumber Textmate Bundle

Ben Mabey wrote: You can get it here: http://github.com/bmabey/cucumber-tmbundle/ This is probably blindingly obvious to anyone who's ever installed a Textmate bundle from github before (i.e. not me), but you have to rename cucumber-tmbundle to cucumber.tmbundle before TextMate will recogniz

Re: [rspec-users] making autotest run other specs

On Sep 18, 2008, at 12:27 PM, "Mark Wilden" <[EMAIL PROTECTED]> wrote: On Thu, Sep 18, 2008 at 9:17 AM, Joaquin Rivera Padron <[EMAIL PROTECTED] > wrote: I'll try to repeat the case in another project, I guess maybe only after autotest reruns *all* the specs (it does so from time to time)

Re: [rspec-users] making autotest run other specs

On Thu, Sep 18, 2008 at 9:17 AM, Joaquin Rivera Padron <[EMAIL PROTECTED]>wrote: > I'll try to repeat the case in another project, I guess maybe only after >> autotest reruns *all* the specs (it does so from time to time) is that *new* >> directories inside spec/ get runned, or maybe I just overl

Re: [rspec-users] making autotest run other specs

oopps, here: all of a sudden I notice that specs in* lib/spec* do really get runned by autotest... i meant: all of a sudden I notice that specs in *spec/lib* do really get runned by autotest... thx joaquin 2008/9/18 Joaquin Rivera Padron <[EMAIL PROTECTED]> > hey Mark you're right, > > all of a s

Re: [rspec-users] making autotest run other specs

hey Mark you're right, all of a sudden I notice that specs in lib/spec do really get runned by autotest... I'll try to repeat the case in another project, I guess maybe only after autotest reruns *all* the specs (it does so from time to time) is that *new* directories inside spec/ get runned, or

Re: [rspec-users] making autotest run other specs

On Thu, Sep 18, 2008 at 6:54 AM, Joaquin Rivera Padron <[EMAIL PROTECTED]>wrote: > I've been spec-ing classes in my lib/ directory, but until now only get > spec to run using: > > script/spec spec/lib/ > > is there a way to make autotest load specs for this directory too? > I know this isn't muc

[rspec-users] making autotest run other specs

hi there, I've been spec-ing classes in my lib/ directory, but until now only get spec to run using: script/spec spec/lib/ is there a way to make autotest load specs for this directory too? thanks in advance, joaquin ___ rspec-users mailing list rspec-

Re: [rspec-users] Newbies are people too

Thanks, Scott. I tend to want to run the real thing to make sure the code really does work. On Sep 17, 2008, at 10:59 AM, [EMAIL PROTECTED] wrote: Ultimately, it's all about how comfortable you feel. Mocks will always smell bad with rails' associations because of the law of demeter violat

[rspec-users] Cucumber branch with a couple of patches

Hi all, We're using Cucumber here at songkick.com and it's working really well for us. I've created a branch here with some extra features that we needed: http://github.com/songkick/cucumber/commits/master Specifically, we've made the transactional fixtures optional in Rails (necessary for when