<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 3, 2008, at 11:07 AM, John D. Hume wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">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.<br> <br>Out of curiosity, Ashley, what size team are you working with where you don't see this problem?<br>-hume.</blockquote><div><br></div>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.</div><div><br></div><div>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.</div><div><br></div><div>Scott</div><div><br></div><div><br></div><div><blockquote type="cite"><br><br><br><div class="gmail_quote">On Fri, May 2, 2008 at 12:06 PM, Ashley Moran <<a href="mailto:ashley.moran@patchspace.co.uk">ashley.moran@patchspace.co.uk</a>> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br> On 2 May 2008, at 06:13, Tero Tilus wrote:<br> <br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I can well imagine how you may end up not getting all the advantages<br> of BDD thru uncommenting process when you compare to clean BDD. But<br> uncommenting is definitely better than writing spec on top of existing<br> code, which in turn is _way_ better than not writing spec at all.<br> </blockquote> <br></div> 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.<div class="Ih2E3d"> <br> <br> Ashley<br> <br> -- <br> <a href="http://www.patchspace.co.uk/" target="_blank">http://www.patchspace.co.uk/</a><br> <a href="http://aviewfromafar.net/" target="_blank">http://aviewfromafar.net/</a><br> <br> <br> <br> _______________________________________________<br></div><div><div></div><div class="Wj3C7c"> rspec-users mailing list<br> <a href="mailto:rspec-users@rubyforge.org" target="_blank">rspec-users@rubyforge.org</a><br> <a href="http://rubyforge.org/mailman/listinfo/rspec-users" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-users</a><br> </div></div></blockquote></div><br> _______________________________________________<br>rspec-users mailing list<br><a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org</a><br>http://rubyforge.org/mailman/listinfo/rspec-users</blockquote></div><br></body></html>