We’ve all heard the hype – that unit testing is a good way, “the one true way” to improve the reliability and flexibility of our systems, to drive out good design, reduce coupling, increase cohesion, write less code, write better code, write faster code, decrease dependencies, write code faster, reduce our carbon footprint, plant native trees, save the whales, reduce orangutan unemployment, counter global warming and colonize the stars.
Some of this hype is thoroughly justifiable. Some ... less so.
Come along to “Unit Testing 101” to see how to make Unit Testing work, not just from a mechanical perspective (how do we write a unit test) but from a philosophical one (how do we write a GOOD unit test).
Bevan Arps is a professional software developer and self confessed geek. With a career that spans analysis to testing, hardware installation to user training, and tech support to technical writing, he is currently a C#/.NET developer working for the Reserve Bank of New Zealand. Bevan’s blog can be read online at www.nichesoftware.co.nz