At work, I’m helping a colleague in developing a material on ‘testing mindset’ which is to be shared to our fellow testers. Initially, we have this list of one-liners — catchphrases that we hope would stick like: Always ask the question why, Assume the product is broken, Trust but verify, etc.
I tried going over them one evening. And while they do emphasize some qualities that are important for testers — like being persistent, curious, attentive to detail, critical-minded — I felt that it was still lacking. Some qualities that I deem important were missing — like having good communication skills, being a team player, being technically skilled, striving for self-improvement, having pride and ownership of your work/craft. I came up with an 8-point bullet list describing qualities that I would like in my test team, until I cut myself short since I was working time-bound. And as I’ve taken a step back from the one-liners to come up with this incomplete list of desired qualities, I took another step back from these qualities and thought of what is the driving force behind the need for these qualities.
Why must testers have those qualities I’ve been enumerating? Why must they keep those catchphrases in mind?
In pausing and taking a step back, I realize it’s all for making things better. I guess that’s my personal testing mindset: I try to make things better.
When I started testing, I thought it was my nitpicking skills and slight OC-ness that made me such a good fit for the job. I just loved finding bugs (and still do)! Over time and over many projects, I found that my purpose in the team isn’t just to find bugs. Essentially, it’s to try to make things better. By “things”, I don’t only mean the products under test. But also my working relationship with my team mates, work loads, schedules, processes, the team itself, and even myself.
- Say, I try to expose the bugs and report them, so that they’d get fix. Product gets better.
- I try to provide suggestions for improvement like a comment on usability. Product gets better. If fixed, that suggestion could cut short the work that the end-user has to do.
- I try to report bugs clearly and concisely. Dev’s life and mine are better than it would have been if i had given a vague report. Dev will hopefully be able to replicate the bug so he won’t have to nag me for details.
- I try to find shortcuts and tools, and share them with the team. Tester’s lives are better. Even just the little things that could help minimize the tedium of some of the tasks we do is something I appreciate.
- I try to read up, and try to continue learning and improving myself. I (hopefully) get better. (Well, i try.)
- I try to encourage knowledge sharing among team members. The team (hopefully) gets better.
Yoda might disapprove, because after all he said “there is no try.” But still, we must persist. The things we do, the qualities we instill in ourselves, our values — these must all drive towards the betterment of our team, our product, and ourselves.