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…
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 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…
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…
This is the 2nd part of the series about analyzing what we’re coding, and therefore which unit tests and integration tests to write. Last time, we talked about the problem we want to test (either unit tests, integration tests or system tests) and a solution design. Once we have those, Read more…
I’ve decided to do smaller releases of “Everyday Unit Testing”, and not wait for full chapters. I’m going to send out emails once a month with the accumulating changes, but releases would be more frequent. As to this one, this is a brief history about how developer testing (unit testing Read more…
Hey everyone, I’m excited, I guess you can tell that. I’ve spent the recent years in the world of unit testing. There’s aLot of information out there. It looks like a solved problem. Yet most developers don’t unit test their code. TDD is even in worse shape This is where Read more…