Yes, I agree with Jarin.
  TDD (Test DRIVEN development) as in tests being to main driver to 
software development is dead (or, more so imho, never really *lived* in the 
first place). Testing code and giving a great importance to having a 
maintained, constantly passing, and rigorous test suite is alive and well. 
This doesn't discount actually writing a test for a feature before you 
implement said feature, which I agree with as a best practice, but test are 
not a substitute for the real stakeholder of your product.

Colin

On Tuesday, May 6, 2014 4:45:36 PM UTC-7, Jarin Udom wrote:
>
> I think it should be made clear that whether or not TDD is dead, *testing* 
> is still alive and well :)
>
> Jarin
>
> On Tuesday, May 6, 2014 1:51:34 PM UTC-7, Rafael Cardoso wrote:
>>
>> ThoughtWorks is organizing a friendly conversation about the death of TDD 
>> between big names in our space. 
>>
>> I thought the group would be interested to watch:
>>
>> https://plus.google.com/events/ci2g23mk0lh9too9bgbp3rbut0k
>>
>

-- 
-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--- 
You received this message because you are subscribed to the Google Groups "SD 
Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to