Open 24/7/365. Never a waiting line! Login and vote now.
By bloid
via guidewiredevelopment.wordpress.com
Published: Apr 30 2008 / 01:54
I’ve had numerous conversations over the past year or so with people who aren’t that familiar with writing automated tests (be they unit tests, functional tests, or what have you), and all the advice I give can really be summed up in one simple rule:
Your tests should break if and only if the product is broken
SaveShareSend
Tags: methodology
Add your comment