Main Page - Books - Links - Resources - About - Contact Me - RSS

Most Popular Help! I've Inherited Legacy Code Testing Untestable Code Continuous Integration... Why Bother? Mock Client Testing The Art of Work Technical Idiot Savants Targetted Skills Aquition vs Free Range Chickens The Habits of Highly Effective Developers

Blog Archive 2005-December 2005-November 2005-October 2005-September 2005-August 2005-July 2005-June

Thu, 18 Aug 2005

One Test per Feature?

Here's a practical way to get your Blitzkrieg Testing rolling. It comes from Johanna Rothman's blog, Managing Product Development.

Here's a short excerpt:

Not every product has smoke tests (a series of tests you can run after each build to make sure the product works well enough to continue development and testing). Smoke tests provide early feedback to developers about their work. So, for the last several years, I've been suggesting to my clients that as they develop a feature, they include one short automated test for that feature in the smoke test. This test allows the developers to know their changes didn't break the product.

...

This isn't optimal, but the people in the group are becoming accustomed to receiving feedback about their work. With the way they'd been implementing "smoke" tests, they prevented themselves from seeing any feedback about their work. This technique might help.

Sounds like another good technique to put in your toolbox...

Enjoy!

Jared

posted at: 20:59 | path: | permanent link to this entry