Skip to main content


This tweet by Kent Beck explains perfectly why I use TDD.

When I was first introduced to TDD and Unit Testing, I was blown away by the fact that I had never thought of writing code to test my other code. I would write code and run the entire application to see if the changes I made worked correctly. I would test the happy path and then pass it on to QA for more verification. I knew that I didn't find all of the bugs in the code, but I also wasn't sure what more I could do to find them. I hated when I got bugs back from QA and worse when the customer found a bug.

I have the anxiety Kent is talking about. It was pretty stressful to deal with this anxiety as I wrote code not knowing how I was going to mess up this time. I would fix something only to introduce a new issue or cause a previously fixed problem to resurface. Then I learned about Unit Tests and TDD and I had a way to alleviate that anxiety. If I was fixing a bug, I could write a few tests that would make sure that bug would not reappear. I could write new code having at least some level of confidence that it would do what I expected it to do.

TDD became my anti-anxiety medicine. It made my code better. It allowed me to relax more about my code. I've often wondered why others didn't seem as interested in TDD as I am, perhaps it is as simple as they don't feel the same anxiety I feel.


Popular posts from this blog

Converting a Large AngularJS Application to TypeScript Part 1

I work on a project that uses AngularJS heavily. Recently we wondered if using a preprocesser like CoffeeScript or TypeScript for our JavaScript would be beneficial. If our team is going to switch languages, we would need to be able to convert existing code over without much pain and we would have to find enough value in switching that it would be worth the conversion. I had read an article that stated that because TypeScript is a SuperSet of JavaScript, you could convert a plain JavaScript file to TypeScript by changing the extension to .ts and not much else would need to change. I wanted to test out this claim, so I took a file that I was familiar with, an Angular Controller, and tried to convert it to TypeScript to see how much effort it would take and then try to figure out where we would benefit from using TypeScript. This is what the controller JavaScript file looked like to start out with: ( function () { 'use strict' ; angular .module( 'app'

Gamify TDD

I like it when things that would not normally be associated with games add concepts from games as a way to incentives you to accomplish things. Why simply go for a run if you can have an app that will track you and give you a gold star if you do better than you did the last time? Why go to the coffee shop that only gives you coffee if the other one will give you points that you can redeem for free drinks eventually? I was recently introduced to C odeSchool , an online training system similar to PluralSight, it has video courses and challenges you can take to prove that you retained what the video taught. CodeSchool also adds badges and tracks to your learning, so as you complete a video and its challenges you get a badge. Complete a collection of courses within a specific discipline and you become a master of that discipline. Some of these incentives are not tangible and really don't mean much in the real world, but they tend to work for me. If I start working towards a large g

Converting a Large AngularJS Application to TypeScript Part 2

In part 1 I was able to take an Angular controller written in JavaScript and convert it to a TypeScript file while doing very little to change the code. In this post I am going to explore transitioning that same controller to actually use the features provided in TypeScript. This is how I left off my controller: declare var angular: any; (function () { 'use strict'; var controller: any = function($scope){ ... } angular .module('app') .controller('controller', controller); controller.$inject = ["$scope"]; })(); While performing the translation from JavaScript to TypeScript, I would make sure at every step that the functionality I expected still worked, so if anything I did broke the system I would change it back and try again with another approach. Also if something seemed like it worked too easily, I would break it on purpose to make sure I wasn't getting a false result through browser caching a previously working