I'm giving a talk on TDD at our local UG tonight, and under the influence of some recent posts here on devlicio.us, I just finished reworking my presentation. This post is an outline for the first half of my presentation. The Problems Code has entropy. That is over time it deteriorates. At least...
While putting together one of my last posts one thought kept scrolling through my head. This was the idea that when you modify your code, you need to make sure your that the intent of your tests still are correct. I know this concept may seem trivial, but how many of us actually do this....
Anyone that is a practitioner of testing or specially TDD knows that the quality of your tests are a direct measure in the assumed quality of your tested code. Better put, if your tests suck, you can assume very low quality from your code. So what is harder, writing quality code or writing quality...
How many times as developers have we made list of things we needed to work on. Most of the time they are 'tasks' in some sort of task management system. However, we do not have one of these such systems at work. So I decided to use 'ignored' tests as my tasks. ...
Test first Test during Test after Answer, Test. No matter what style of testing you believe in, they all share one common trait. They all test your code. So, what is the point of this post you may ask? Simple. To me, it does not matter how your tests come to be, but having tests is what is important...