Reginald Braithwaite-Lee makes a long post on lessons learned from failure. Excerpt: "If you must refactor, refactor here, and there, and there to solve this, and that, and the other specific problem that has a specific feature or bug attached to it. And show me that you had 100% unit testing coverage on the affected code and completed each refactoring in a day or so and then ran all the unit tests and got a green light. If you can't do that, you're going to fail."

Alaistair Patrick investigates a way to automatically detect all memory leaks at compile time with unit tests: "Is it possible to automatically detect all possible memory leaks at compile time? In general, and certainly for C-style programs, I think the answer is no. But if a program is structured in a certain way, the answer is definitely yes."

Michael Stal introduces unit testing in C# with a basic example.

Choong Yong Koh highlights a maven test:test classpath problem giving rise to java.lang.LinkageError.

Tim Weaver writes FxCop rules, and wishes for a way to bind TDD and code analysis.

John Lam writes his first C# unit test using Python.