Unit Tests Anti-patterns: TDD without refactoring
Anti-patterns are patterns with negative consequences. In this series I’m going to tackle those patterns, explain what they signify in terms of risks, and what to do instead. Let’s look at a pattern common to people who start out on their TDD journey: They forget to refactor. When they do, Read more…
TDD In Real Life – Part 2
Last time we’ve started talking about how to approach TDD in real, complex systems. While plain vanilla TDD assumes nothing about the world around our component, in real life, there are constraints we need to relate to. Where we stopped, we talked about rethinking the order of work, based on Read more…
TDD In Real Life – Part 1
TDD comes from the world of unit testing. It’s optimized for small pieces of code; small increments of functionality. BDD takes the test-first approach, adds functional and user semantics and tries to follow the same formula for the whole software. TDD helps us build a class or a module. But Read more…
New Version of “Everyday Unit Testing”
That’s right! It’s been a while, but lots of content going into the new version, which you can download right now. What’s added? Two new chapters: Testing strategy – how to think about testing (and unit testing) a feature. TDD – My take on TDD. It’s still got long to Read more…
Legacy Code to Testable Code #13: The Testable Object
Other awesome posts in the series: If the code we want to test is highly-decoupled from its dependencies, we probably don’t need to do anything to it. But when we have a medium-big ball of mud things change. There are parts we want to ignore or control through mocking, and Read more…
TDD: It’s Not That Simple
TDD is pretty simple right? Obey the red-green-refactor step-by-step and you’re on your way to glorious, non-legacy code. It’s really easy to explain. The rules are easy to follow. Why then so few people actually do it, and when they do, so few actually do it well? In my talk Read more…
How Can I Write A Test If The Code Is Not There?
Introducing TDD is a lot more psychological than you think. When we start introducing TDD we need to think about how people new will react. For example, the first question that people ask is: How am I going to write the test if I don’t know what the code does? Read more…