Re: [PhillyOnRails] rspec slides

["Jason Yates" <jaywhy@gmail.com>]

> It just seems like a tradeoff to me.  The more time you put into
> testing, the less time you have for coding, but the more reliable the
> code is.  So the question is, for project X, is it better to churn
> stuff out quickly and have a harder initial maintenance cycle, or have
> a slower development cycle with higher confidence?  Surely the answer
> is "it depends..."

I think it is more "it depends extremely rarely..."  In my experience,
the trade off point is extremely low.

Testing is more about design than code reliability.  Using your API's
before you actually create them, makes better API's and a better
design.

Testing makes refactoring a feasible operation.

Testing also helps you know exactly where you are in the development
process.  Just run the tests and see what fails, no need to stop and
think "where am I" and look back over notes, whiteboards, etc.

Not to mention it makes the code more reliable.  I sort of miss the 6
a.m. wake up calls saying the code update broke such and such.

I could go on about the benefits.  Whole books have been written about
them.  The bottom line is test ;).

-- 
Jason Yates
jaywhy@gmail.com
_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk