Building a better mousetrap
September 7, 2004
My first project that I plan to release, DynamicImage, isn’t groundbreaking or revolutionary. There are plenty of other components out there that do the same thing. However, I’m using this project, which is relatively small, to fine-tune my development processes and habits. I believe that incorporating as many of these tools as possible ultimately leads to a better development experience as well as a better product. You can find out more about the tools by following the links or by Googling on “test driven development” or “continuous integration”.
- NUnit
- NUnitASP
- FxCop
- NCover
- NAnt
- NDoc
- CruiseControl.NET
- Draco.NET
- Log4NET
- Any of the Microsoft Application Blocks
I wish I could say that I am using them all and that they are deeply embedded in my processes. Unfortunately, that is not true. But I am making progress. I am using NUnit to test my DynamicImage control as I develop.
It’s working out better than I expected. I’ve got about 50 tests in a abstract test class which is implemented by landscape, portrait and square image test classes. So with one click I can run 150 test cases on the control. So far this is just for the Resize method. It’s been great being able to make a change and validate that nothing broke so quickly. The logic in resize isn’t that complicated but a couple of tweaks I am adding might work with one image type but not another and NUnit quickly works through all of that for me.
I’m hoping that I will be able to use NUnitASP to test the HttpHandler portion the control. After that is probably NDoc. Once I get those done, then I will be ready to release my first version.
Popularity: 5% [?]
Comments
One Response to “Building a better mousetrap”
Got something to say?
You should consider adding CodeSmith to your list at some point.