Travis B. Hartwell / Software Craftsman

I finished reading "Extreme Programming Explained" today. It's part of my thinking of the best practices and things I want to learn as I move onto professional development and working on my own open source projects. In my current situation, I can't adopt all of the Extreme Programming practices, such as pair programming. But one that I can adopt is the use of Unit Tests. I have watched Twisted progress over these last couple of years. It now has nearly 1200 unit tests (taking a quick glance at the buildbot to find this out). I don't doubt that the existence of these tests helps ensure the integrity of a system as large as Twisted. Just this observation alone has converted me to the practice.

This is something that I believe is useful. Unfortunately, I have found it difficult to write unit tests for my own code. I look at the code I have for Informant and wonder how unit tests can fit in it. Even after looking at the tests for Twisted, I still have a difficulty in writing tests for my own code. I don't know why I am having this block. It is a practice I want to adopt...