Every so often I come across the question "should we use return codes or exceptions to report errors."

This article is based on an overview that I wrote to help introduce developers on a pilot project to unit testing. It covers the strategic reasons for using unit tests and the tactics of writing a unit test harness using the freely available JUnit framework to minimise the work involved.

After reading Nigel Eke's series on Monopoly in Overload, it occurred to me that there might be interest in seeing the process of bringing a commercial game to market.