Looking around at the blogosphere, OSS repos and conferences, it might be easy to assume that test-driven development is all about frameworks — unit-testing frameworks, mocking frameworks and frameworks for dealing with frameworks.

Most frameworks evolve as responses to other frameworks, which means they are often anchored (or stuck) in a particular point of view. And often that point of view is fairly narrow and, somewhere along the line, influenced by JUnit. What makes TDD effective is focus, clear progress and expression of intent; frameworks do not typically change what is possible, simply what is convenient.

This talk reconnects with the essentials by taking a lo-fi approach to framework usage.

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.