How To Write Hard To Test Code & What To Look For When Reviewing Other Peoples Hard To Test Code

October 28th, 2009 · 5 Comments ·

Here are my slides which Cory Smith and I have presented this morning at OOPSLA 2009.

The ability to write hard to test code is innate in every developer form the moment we have built our first “Hello World” application. It is so automatic that we do not even know when we are doing it. On the other hand writing testable code requires that you un-learn this behavior. In this tutorial you will learn how to recognize the red flags in the code and what are the common solutions for them. We will look at sample code representing common development practices and look into subtleties why this code is hard to test and how to fix it. The goal of the tutorial is to arm you with knowledge of how to write code which can be tested using small focused tests.

Slides: view slides in PDF format here

Tags: Uncategorized

5 responses so far ↓

Josh Szepietowski // Oct 28, 2009 at 1:47 pm

Any chance that there was a video recording of your presentation that will be surfacing at any time? The slides seem to infer that I am missing a lot of valuable things being said..
Ilias Bartolni // Oct 28, 2009 at 3:15 pm

Thumb up!
Excellent tutorial…

Josh …unfortunately I didn’t see anyone recording it.
Mark // Oct 28, 2009 at 3:25 pm

Interesting stuff as always, Misko. I particularly liked the Law of Demeter comment about the wallet — very concisely put
Kartik // Oct 30, 2009 at 7:45 am

Looks like something really important is being said.

Please post slide notes/audio if video not available.
Bele // Nov 14, 2009 at 11:10 am

Please post slide notes/audio if video not available.