Daniel Cazzulino's Blog

From Pablo's announcement:

I wrote before about What's wrong with the Record/Reply/Verify model for mocking frameworks, and in that context, why Moq didn't provide a mock verification functionality.

Most projects use "Warnings as Errors" project-level setting together with the "XML documentation file" so that you can spot early on which areas of your public APIs are not documented or have broken links etc. in it. I've come to rely on it, especially in the face of refactoring, which even in VS2008 still doesn't refactor code documentation references.

Lately, there's been some formalization of the definitions of mocks, stubs, fakes and dummies, which Fowler popularized through his site with his article Mocks aren't Stubs by introducing the concepts from Gerard Meszaros' xUnit patterns book. I haven't read the book, but the definitions are sensible.