Skip to main content

Test Driven Development Doesn't Mean Test First

I’m a fraud and here’s why.

I am a huge advocate of Test Driven Development (TDD). I’ve even written an introduction to TDD. In his book Test Driven Development by Example [TDDbyExample] Kent Beck defines TDD as a process where you must write tests for code before writing the code itself. Therefore if you’re doing TDD you have to write the tests first, right? Wrong!

I really feel like unburdening, so here’s another admissions. I’m addicted to the green bar and high code coverage percentages. For those that are unfamiliar with the green bar, it’s a feature of the JUnit (and other testing framework) GUI. If all your tests pass you get a green bar. If any of your tests fail, you get a red bar. I’m addicted to the green bar, I can’t sleep without it. There are tools that allow you to measure how much of your code is exercised by your tests as a percentage. Usually anything over 80% coverage is considered good. I always strive for 100%, but usually achieve high 90s. I can’t sleep without high code coverage either. It’s very important that you bear these two vices in mind as you read on as they give me a discipline that not all software developers have. This isn’t because I’m some super software developer. It’s an affliction, believe me. If you don’t have this discipline, write your tests first.

There are many advantages to TDD. The two that stand out for me are loosely coupled code and code that’s easy to test (obviously). Actually by making your code easy to test it becomes loosely coupled and easy to change by default and that’s the point I’m making. If you want to get the green bar and have high code coverage then you need to make your code testable. Writing the tests first forces you to make your code testable, but it’s not the only way. If your tests are automated and measuring code coverage is automated or better still your continuous integration system runs your tests and measures the code coverage you’re forced to make your code testable. The key, when writing your code is to think about how you’re going to test it and write the tests soon after. This is a skill that has to be learnt and the best way to learn it is to start test first. Once you have it nailed though, you too will become addicted to the green bar and high code coverage. Of course you still have to write the tests, before you’ve written too much code, and refactor to remove duplicate code. It’s important to keep running the tests and to make sure they pass every time you make a change to the code. Many developers are lazy and don't bother. My affliction means that if I'm lazy, I don't sleep. It's a curse.





Comments

Post a Comment

Popular posts from this blog

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...