title: Unit testing Anti-patterns catalogue
body: <p><strong><a href="http://en.wikipedia.org/wiki/Anti-pattern" rel="noreferrer">anti-pattern</a></strong> : there must be at least two key elements present to formally distinguish an actual anti-pattern from a simple bad habit, bad practice, or bad idea:</p>
  
  <ul>
  <li>Some repeated pattern of action, process or structure that initially appears to be beneficial, but ultimately produces more bad consequences than beneficial results, and</li>
  <li>A refactored solution that is clearly documented, proven in actual practice and repeatable.</li>
  </ul>
  
  <p>Vote for the TDD anti-pattern that you have seen "in the wild" one time too many.<br>
  <a href="http://blog.james-carr.org/2006/11/03/tdd-anti-patterns/" rel="noreferrer">The blog post by James Carr</a> and   <a href="http://tech.groups.yahoo.com/group/testdrivendevelopment/message/20745" rel="noreferrer">Related discussion on testdrivendevelopment yahoogroup</a></p>
  
  <p>If you've found an 'unnamed' one.. post 'em too. <strong>One post per anti-pattern please</strong> to make the votes count for something.</p>
  
  <p><em>My vested interest is to find the top-n subset so that I can discuss 'em in a lunchbox meet in the near future.</em></p>