[rspec-users] Cucumber step definitions vs. RSpec examples

Brandon Olivares programmer2188 at gmail.com
Mon Mar 30 07:08:36 EDT 2009

> -----Original Message-----
> From: rspec-users-bounces at rubyforge.org [mailto:rspec-users-
> bounces at rubyforge.org] On Behalf Of Zach Dennis
> Sent: Sunday, March 29, 2009 11:10 PM
> To: rspec-users
> Subject: Re: [rspec-users] Cucumber step definitions vs. RSpec examples
> > I like a lot of what Steve is saying. To summarize and communicate in
> my own way...
> It is good to know how and when to do something. Like writing view
> specs and controller specs. If you don't know how then you'll never
> know when. Sometimes learning to take small steps seems ridiculous,
> but it's by being able to work in small steps that you can be
> confident about making larger ones.
> Here are three questions I ask myself when I get frustrated:
>  1 - Am I doing it wrong?
>  2 - Should I be doing this in the first place?
>  3 - Am I experiencing a skills deficiency?
> Usually I think it's #1 and then I quickly jump to #2 when I don't get
> it resolved in 5 minutes of googling. And then I find out a day later
> it was because of #3 and I needed to go home and practice a little
> more so I better understood what I was doing, why I was doing it, and
> how I could leverage the tools to make it easier.
> We all learn to make good decisions by first making bad ones, and
> practice lets us do that w/o putting giant turds in an application's
> production codebase.

Thanks for that explanation.

For me, it's either TDD or BDD, honestly. I've experienced the assurance
having tests for nearly every line of code affords me, and don't want to
forgo that. But I like the semantics of BDD a lot better, after reading the
RSpec book.


More information about the rspec-users mailing list