- Agile Leadership Development
- AgileSafari
- Coaching
- Facilitation
- Leadership
- Practices
- Principles
- Product Owner
- Scaling
- ScrumMaster
A History of Test-Driven Development (TDD), as Told in Quotes
Nope, I haven’t forgotten that my next newsletter was going to be in response to a comment on the last newsletter. But I’ve discovered the need for some diagrams, or code, or something other than prose, to explain myself succinctly. So, it’s taking longer than
Can a Unit of Behavior Span Objects?
A client recently asked me if a unit test could test multiple objects. On the surface, you might suppose my immediate answer would be “No way!” But his question, and my answer were both a bit more nuanced than
A Dozen Reasons Why Test-First is Better than Test-Later, Pt. 3
The third and final part in the Developer Essentials mini-series of posts about test driven development (TDD). Click here, if you missed Part 1 or Part
A Dozen Reasons Why Test-First Is Better Than Test-Later (Pt. 2)
From the Developer Essentials Newsletter: The intersection of Agile methods and technical software development.
A Dozen Reasons Why Test-First Is Better Than Test-Later (Pt. 1)
An editor of Dr. Dobbs magazine once wrote to me—replying to my response to an article—“All the benefits [of Test-Driven Development] could be attained equally by writing tests after the code, rather than before.”[1]
Tests exercise software to be sure it’s doing what was intended. So, whether you use Test-Driven Development (TDD) or write unit-tests