In the previous installment, we discussed how to identify dependencies and replace them with Test Doubles in order to properly unit test them. I demonstrated one way to do this by defining vital functionality in abstract base classes, then creating … Continue reading →

In the last post, we learned about the different types of tests, and how they differ in scope and purpose. In this post, we’ll figure out ways to limit the scope of tests by controlling the behavior of external dependencies, … Continue reading →

As we iterate through the TDD process, we’ll build up a large suite of tests. When writing so many tests, it is easy to lose focus of the scope and the purpose of each test. There are three broad categories … Continue reading →

There comes a time in every codebase’s lifetime where you’re forced to admit you screwed up. Maybe not in a fatal way, like having critical bugs or failing to fulfill a contractual requirement. Sometimes you can do the right thing … Continue reading →

Test-Driven Design is a big buzzword these days – but what does it really mean? Martin Fowler explains it thus: Test-Driven Development (TDD) is a technique for building software that guides software development by writing tests. It was developed by … Continue reading →

We stare at a blank slate. An empty project. Where do we go from here? I usually start by identifying the core concepts and the entities, and start creating classes. For me, thinking about how things are conceptually defined and … Continue reading →

Over my career, I’ve done more than a few code reviews, brown bags, and presentations for my coworkers. It’s more than just teaching them how to write code that works, for that is the least interesting thing (albeit the most … Continue reading →