John D. Hume
duelin.markers at gmail.com
Sat May 3 11:07:21 EDT 2008
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
Out of curiosity, Ashley, what size team are you working with where you
don't see this problem?
On Fri, May 2, 2008 at 12:06 PM, Ashley Moran <ashley.moran at patchspace.co.uk>
> 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.
> rspec-users mailing list
> rspec-users at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rspec-users