Six Rules of Unit Testing

Devankur's Collage : Potpourri of IT Management, Technology, Global Delivery, Testing and ADM "It ain't braggin' if you can do it."-Dizzy Dean, 1930's baseball player

<< Of names.. | Home | Rules of 'Zero-Defect Software Development' >>

Comments (2) | Share

Check out this Six Rules of Unit Testing by Charles :

Write the test first
Never write a test that succeeds the first time
Start with the null case, or something that doesn't work
Don't be afraid of doing something trivial to make the test work
Loose coupling and testability go hand in hand
Use mock objects

http://radio.weblogs.com/0100190/stories/2002/07/25/sixRules
OfUnitTesting.html

Posted on Tuesday, July 5, 2005 6:25 AM Software Testing | Back to top

Comments on this post: Six Rules of Unit Testing

# re: Six Rules of Unit Testing

Very useful for begginers ))

Left by Kenny on Jul 12, 2006 7:12 PM

# re: Six Rules of Unit Testing

What I observed is that in language like java usually the easiest way to reuse code is inheritance. That leads to ugly software that is difficult to test and read. Composition over inheritance is simple and useful rule. It’s way easier to explain and adopt than elaborating on OOD&A (which as you say just few programmers actually know).

Thanks for the rules! I'll never forget that.

Left by raised air bed on Apr 27, 2009 11:09 PM

Your comment:

Title:

Name:

Email: (never displayed) (will show your gravatar)

Comment: Allowed tags: blockquote, a, strong, em, p, u, strike, super, sub, code

Verification: