Recently I did a 99 second talk at TestBash in Brighton in which I compared golf to testing:
Now I know golf is a rather dull subject to many people who may have never played it so I’ll try not to bore you all too much. 😝
The thing with golf as anyone who has ever watched it on TV knows is that you only ever need a single golf club to play golf at the highest level… Rory McIlroy, Sergio Garcia, Seve Ballasteros, Tiger Woods… They all only ever used one club! Let me explain…
- Those guys tee off using a driver to hit the ball as far as possible. BOOM and down the fairway the ball flies.
- Then they use the driver again to punch the ball down the fairway or onto the green.
- And if they hit it into the rough or a green side bunker guess what club they teach for? That’s right, the driver!
- Then they’re a foot from the pin where just a nice little tap in will win the hole. What club do they use?
Except that actually nobody uses one club all the time because at the very best professional level in golf it would be inefficient (and for the vast majority of weekend warriors it makes the game completely inaccessible and not even remotely enjoyable.)
Every golf club has a purpose and an ideal use case; some clubs have multiple purposes or several use cases but no club fits all the purposes and all the use cases and yet I’ve met testers who apply that “one tool fits all” mentality to their testing daily!
I’ve met testers who use one set of browser developer tools and never try others (even berating others without trying them!) and I’ve met testers who have a certain choice of tracking their exploratory test coverage and they never look into other possibilities:
- Is a notepad doc sufficient, useful and logical for others to read?
- Would Rapid Reporter give the notes more structure?
- Is the time trade-off worth the benefit to YOUR context?
- Should you be tracking coverage in a spreadsheet because your client is a 3rd party who requires a visual representation of the testing done?
- Does your tool integrate directly with your issue tracker? Should it?
Do people in YOUR context regularly evaluate your testing tools and techniques to make suggestions on improvements or do you sit quietly and not question the status quo?
For a long time I myself had one single choice of Proxy software to analyse what’s being sent from and fired back to a test app. I knew what I could do with it so I never looked into others, what was the point when I knew my choice of app well?
Sometimes tools can be used for purposes other than the intended one, much like someone may choose to “bump and run” a golf ball from the fringe of the green with a club normally intended for long shots off the fairway – For that specific shot it’s a great option. For that specific test you want to do perhaps cURL + JQ is a superb option to pull in some JSON and reorder it for comparison but for the rest of your testing there may be little value in those tools.
As testers we should strive to read about tools, try tools out, make notes on how you might use those tools best in your daily testing work and then maybe leave the tool alone until the task at hand DEMANDS that tool!
Maybe that will put us in a far less biased position when it comes to using the right tool for the job and it will expose us to more tools, better tools and ultimately make us more efficient in our day to day work.
The driver is not the best club for all shots all the time.