unit testing

1. Forgetting Red to Green
2. Poor Naming Conventions
3. Unclear purpose
4. Code Organization
5. Unit vs Integration Test Confusion [24:06]
6. No Code Coverage on Exceptions
7. Giving Up On The User Interface [50:04]
8. Fixing Bugs Without Unit Tests
9. Useless Code Coverage
10. Stop Mocking Me!

Bonus:

• Giving Up On Legacy Apps
• Un-testable Architectures
• Not Doing Interface-Driven Programming
• Not Doing Dependency Injection

Phrases...

• 
  
• QA's Are People Too... you'll really should treat them ... they are human beens [53:00]
• Just because you have 100% code coverage, doesn't mean that your code works. It only means that you've executed every line. (Scot Hanselman).

http://www.msteched.com/2010/NorthAmerica/DPR204

Unit Testing SharePoint Webinar And Presentation.