I’ve just been reviewing my TDD/BDD presentation. I’m giving it at http://www.njdotnet.net/ on Thursday May 14 at 6PM. The state of the art has advanced considerably since last year when I first put the presentation together. Of particular interest are the new mocking framework, moq(download at: http://code.google.com/p/moq/wiki/QuickStart) - and the SpecUnit extensions (download at: http://code.google.com/p/specunit-net/, more info: http://www.code-magazine.com/article.aspx?quickid=0805061&page=4).
Moq flattens the learning curve for using mocks. It hides record and playback providing modeless mocks. This allows developers to focus on using the mocks, not on arcane mock configuration rules, like when expectations can be set.
SpecUnit moves BDD terminology and structure into the comfortable confines of the NUnit world. The extensions and tools added by SpecUnit facilitate implementing executable specifications and add to their communication value for developers and stakeholders alike.
I’ve revised the section of my presentation on mocking to use the Moq framework and the new “test double” terminology. Before I give the presentation again, I’ll revise it to use SpecUnit, and take advantage of the context-observation structure, so that instead of showing an NUnit test window, I can show a customer-ready report.
That’s it for now.