Pair Testing

27 November

Pair testing isn’t new and in fact, it has a more well-known cousin in Pair programming. What it does well is that it allows for two different sets of eyes testing the product. Essentially one is the *driver* and drives the keyboard whilst the other is the *observer* or *navigator* (I prefer navigator – its name suggests a more hands on role.) The navigator is there to suggest ideas, learn, be mentored, mentor, record, find information etc.  These roles are of course, interchangeable, and allows for a very shared, creative testing activity (of course there are challenges as there are in any approach but we won’t discuss them here.)

As we were testing, we interchanged a number of times and discussed and discovered a number of bugs. This is one of the benefits of pair testing in that brain can be engaged on task longer and is a lot fresher because of the role swapping, different perspectives and the exchange of ideas they will come flowing.

I’ve been involved with pair testing and it works. I have also seen it in action and it's an approach that we should consider more often!


Posted by Brian Osman