Effective testing should be done to ensure that a Product solves the business problem, in the way it was intended. It also seeks to prove that no change to the Product harms an existing working system. (It’s a much deeper topic than we can cover here.) These are the goals of Quality Assurance. So I […]
Test Driven Development
Debunking misconceptions about Test Driven Development; including effectiveness, writing tests after code has been written, and impact on program architecture.
While Test Driven Development is challenging to learn on your own, TDD has tangible benefits that can’t be achieved by writing tests after the fact.
My experience running a TDD Randori session, using Danilo Santo’s paper on Brazilian Coding Dojo as a guide. Inspired by Dave Nicolette’s session at Agile 2008.
Responding to ‘Test Driven Development considered harmful.’ The primary benefits of TTD are simplified design, cleaner APIs, decoupling, and reduced bugs.