One way or another, all software that is put to use gets tested. In most of my projects, testing is usually an ad hoc affair where I make the program jump through whatever hoops come to mind. Users, in their ignorant blind trust, disregard my instructions on how to use the program and discover entirely novel ways to destroy what was, in my hands, a working application. Over the years, I've developed my own strategies for testing, centered on console applications. In The Art of ...

REGISTER NOW TO ACCESS THIS ARTICLE

All registered users get access to premium content on iPro Developer for free.

Already registered? here.