[rspec-users] BDD/Rails/Shoulda
Scott Taylor
mailing_lists at railsnewbie.com
Sat May 3 17:01:51 EDT 2008
On May 3, 2008, at 11:07 AM, John D. Hume wrote:
> Even when working test/spec-first, when I'm pairing with someone who
> isn't experienced working that way, I find myself constantly saying
> "I'm pretty sure we don't need that yet." (I've just written the
> spec my pair is trying to get passing, so I know how little code we
> need.) If it happens then, it will certainly happen when that same
> developer is uncommenting code already written.
>
> Out of curiosity, Ashley, what size team are you working with where
> you don't see this problem?
> -hume.
I remember a joke that Aslak mentioned a while back ago on this list:
He had a friend (or co-worker) who wanted to write a tool which would
delete every line of code which didn't get covered with rcov. I found
that remark funny because Aslak didn't know if his co-worker was
joking or not.
Now that I think about it more, it probably wouldn't be a bad idea to
have such a tool like this, even if it was just for didactic purposes.
Scott
>
>
>
> On Fri, May 2, 2008 at 12:06 PM, Ashley Moran <ashley.moran at patchspace.co.uk
> > wrote:
>
> On 2 May 2008, at 06:13, Tero Tilus wrote:
>
> I can well imagine how you may end up not getting all the advantages
> of BDD thru uncommenting process when you compare to clean BDD. But
> uncommenting is definitely better than writing spec on top of existing
> code, which in turn is _way_ better than not writing spec at all.
>
> Perhaps "uncommenting" is a bad description. What I do is write
> specs for the behaviour I want, and see what bits of the code (if
> any) do that. (Which will obviously be pretty similar to the what
> it does anyway.) What I *don't* do is pick a line of code and write
> a spec for it so I can uncomment it. I guess that's how you would
> run into trouble.
>
>
> Ashley
>
> --
> http://www.patchspace.co.uk/
> http://aviewfromafar.net/
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20080503/d3376391/attachment.html>
More information about the rspec-users
mailing list