Exploratory Testing has its origins around the turn of the century (sounds historical doesn’t it) when one or two enterprising individuals dared to suggest that perhaps developing test scripts and executing them wasn’t the only way to test software. Fast forward to today where Exploratory Testing is a well-accepted practice that some individuals swear by (and some even more than that!). However, one the challenges that Test Managers are always faced with when deploying is how to track and measure progress from a technique that by its very nature, is not given to providing many mechanisms to measure against. Let me share with you an approach that I’ve developed by building upon the suggestions and innovations of others from within this discipline that can build into a full set of indicators and meaningful information to keep any project manager happy.
