The Daily Build

Icon

Software Development, version 3.0

The cost of (not) testing software

Tweet this post

Great post on the cost of (not) testing software. The take-home lesson is “find defects early”.

The main thing missing from the discussion is that there are better techniques for finding defects than testing. Like design and code reviews, and especially more attention to requirements. Catch defects as early as possible and reduce costs even further.

No TweetBacks yet. (Be the first to Tweet this post)
Share and Enjoy:
  • del.icio.us
  • Digg
  • TwitThis
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks

Related posts:

  1. Five Reasons to Slow Down
  2. Jason Cohen on QA vs.QC
  3. The Toolkit of a Software Engineer
  4. Makefiles are Software Too
  5. Removing Defects From Django Apps

Category: process, reviews

Tagged:

Leave a Reply

My Tweets

  • Pondering the potential benefits of quick sprints. One week? Two? 05/12/09 02:39am
  • I'm back online now after a brief hiatus caused by zero bandwidth from new temporary location... 04/02/09 02:20am
  • heh, BDFL retires - http://www.python.org/dev/peps/pep-0401/ 04/02/09 02:18am
  • Boston has PyCon envy - http://python.meetup.com/181/ (see you there) 03/18/09 02:17pm
  • Plan to throw one (or two) away, you're going to anyway: http://www.javaworld.com/community/print/2537 03/11/09 02:44pm
  • Categories