Found by .net brew
Agree with Karl
1. Unit Testing is design activity
2. Integration tests are must
3. Write Unit test to test non-trivial code
4. Code coverage is not important.
5. Invest in logging
Unit Testing Strategy , architecture and framework has to done by Architects and Leads.
Developers need help from Architects and Leads.
Review your unit, integration tests at regular interval
Hopefully smart unit tests will make it easier to write unit tests.