A good and useful summary, and it would be great if more people could get on board with the concepts outlined in the video.

I've developed a simple approach for applying the techniques - when implementing a feature, I first write Gherkin specifications (Given..., When... Then...) as inline comments in my unit test code, and then pad out the implementation. This captures a refactor-proof specification alongside the implementation code, and can be applied on a case-by-case basis (i.e. sometimes a test may be written without a spec - this is a dead giveaway that it's a throwaway test).

Also it's much easier to nudge a team in the right direction by doing this, than it is to convince the team to adopt BDD and a new testing framework.

Funny. I use the comments-first approach too. Nice

Nice post Rob. Nice also to see some sense coming back to testing. The increase in the popularity of mocking has been a concern for me. It's a useful tool but there's no need to break down simple or even moderate apps so intricately and completely. I've always found the result more pain than gain.