Tag Archives: testing
Lately, I’ve been trying to get caught up and remain caught up with daily content: empty email inbox, no unread Slack messages, and now, all RSS feeds read. It’s the last of these that led me to a fascinating discovery.
Seen on DamnLOL… Ninety-nine little bugs in the code, Ninety-nine little bugs! You take one down, patch it around, A hundred and seventeen bugs in the code! (See also Twelve Benefits of Writing Unit Tests First.)
Software developers have a wonderful explanation for why there are so, so many software bugs. Unfortunately, it’s a highly technical explanation that’s very difficult for the layman to understand. I’ll try to summarize, but be aware that the following is … Continue reading
Why do programmers hate writing unit tests? Why do they hate even more writing unit tests before coding? You don’t have to answer. I’ve already heard the excuses. These are rhetorical questions. I have a theory, however, what the real … Continue reading
Working on a team that’s not yet onto the value of unit testing, I frequently encounter what Michael Feathers calls “legacy code.” It is not unit-tested and can’t be. That doesn’t mean I need to forget test-first.