Temperature: 18 degrees celcius. Woohoo!

This has been my first summer in Canberra since I moved up here with Monash.NET. Before that I was living in Melbourne, and grew up in Brisbane (Caboolture actually). In Queensland summer is humid, but atleast there is a good chance of rain most evenings. Melbourne is much drier during summer but cool changes do come through quite regularly, and the temperature is very predicable – look at the weather in Adelaide and add a day.

Canberra, however, has been a real shock to the system. Because there is no body of water to regular the temperature it can climb and climb and climb. For the last month or so we have fairly consistently been in the 30^oc to 40^oc (thats up to 104^of if you don’t have a converter handy). While its not the surface of the sun, it does make getting a good night sleep quite difficult – you always feel tired.

Well, today I had to put on a jumper. In fact I am wearing this spiffy canterbury MVP jersey that  Rose (local MVP contact) sent me. If you have an appreciation of real football (apologies to soccer fans – this isn’t directed at you), then you will know just how warm these things can be. The current temperature is down to 18^oc, and while it might climb during the day I can’t see it getting over 30^oc.

I’m looking forward to looking out on the snow frosted hills this winter. Last year it snowed a number of times but I was unlucky enough to be delivering training courses or working interstate each time.

So, who spotted the bugs in <csunit />?

When I first introduced my task to the world I mentioned that there were a few things that I wanted to tackle in future releases. Here is a bit of a referesher for those of you who missed my earlier post.

• Write automated unit tests using csUnit.
• Write automated build script to run unit tests and build a release.
• Improve API documentation for the source code using XML comments.
• Make the NAnt output look prettier.

I am now pleased to annouce that in the 1.1.0.0 drop I have started to address the first two items in that list. There are now a bunch of unit tests in the NotGartner.Build.Tasks.Tests project to excercise the task and weed out any problems with future modifications/enhancements I make. The act of writing the unit tests actually uncovered a number of bugs which are now fixed.

• When input validation failed, clean-up of temporary files still occured causing an exception, masking the underlying exception that was raise as a result of invalid arguments.
• Test summary output failed when tests passed (can you believe I missed this!).

Both of these errors resulted in me not running a full suite of tests as the task evolved, so things slipped through the cracks. Anyway, give this drop a crack!