On the bus the other day I overheard a woman discussing her upcoming nuptials. She was quite the modern girl, it seems, and was not going for any of the traditional ceremonial wedding stuff. Well, maybe a small wedding party, like three bridesmaids and three groomsmen, definitely no more than that! And certainly no flowers, no boutonnières, no tossing of the (non-existent) bouquet, no dancing, and no wedding cake. “I want this to be about me getting married”, I heard her say, “not about all this wedding stuff. I want it to be a party!”
Another conversation I overheard was between a young man hauling “Mass Transit Now” lawn signs (we have a large mass transit expansion proposal on our November ballot) and an older man who had bicycled to his bus stop. The older man commented that taking the bus to plant the lawn signs seemed apropos. The younger man replied that he never took a car. “Never?” rejoined the older man; “That’s stupid!”
I see connections to testing in each of these overheard conversations. I often see testing approached with great ceremony. Teams form traditions around how they test and seem to forget they could work in other ways. The ceremony with which they test becomes all-important, performing each of the steps in their testing ceremony becomes paramount, and no one dares to (or even thinks of doing) their work any other way. They appear to have forgotten that testing is about providing information to their stakeholders, not about following a process or performing a ceremony.
The woman I overheard was dispensing with ceremony and tradition insofar as they did not fit her idea of an ideal wedding – insofar as they got in the way of her celebrating her marriage. Similarly, the best testers I know dispense with the ceremony and traditions they and their teams have accreted around testing and get on with the business of providing information to their stakeholders. The soon-to-be-bride wanted her wedding to be a party; great testers love testing so much that they cannot help but party every moment they are testing!
The Mass Transit Now guy takes bus riding to a point his seatmate evidently considers extreme. The best testers I know continually do the same and take their testing to a point their developers, program managers, and even fellow testers consider extreme. This might mean writing test automation rather than testing manually, testing manually rather than writing test automation, or deciding that a particular piece of functionality does or does not need any (more) testing when everyone else believes it does not or does. Regardless of what they are doing that seems extreme to the rest of their team, they are confident of their decisions and the reasons behind them, even if their colleagues think these reasons and decisions are stupid.
What kind of tester are you? Do you follow traditions and partake in ceremony and go with the crowd? Or do you evaluate each situation as it arrives and decide what is your Best Option in that particular case? Whichever you do, how is that working for you? Let me know!
*** Want a fun job on a great team? I need a tester! Interested? Let’s talk: Michael dot J dot Hunter at microsoft dot com. Great testing and coding skills required.