Test your changes

April 30th, 2008 by Xerxes Leave a reply »
  1. Make sure you test your changes. end to end.
  2. Make sure you write unit tests to cover your code. Every possible line
  3. And for the love of God, don’t ask me to review your work when you haven’t taken the time to test it yourself. Not only do you waste my time, but you waste YOUR time which could be spent fixing the problems I discovered anyway.
Be Sociable, Share!

Related posts:

  1. Test This is a test HTML Email!www.xerxesb.no-ip.org...
  2. Test your web design in different browsers After seeing the fully CSS Homer Simpson, i wanted to...
  3. Shadow Copy Cache Hell This post may be terse and may possibly contain profanity....
  4. Unit-Testing Setup/Teardown: Purist vs Practical I’ve been wondering recently whether it’s important to take a...
  5. Instant Twitter Bookmark Tonight’s been a busy night for silly coding This first...

Comments are closed.