Wednesday, August 10, 2011

Tester by association

Are you often referred to by other teams in your organization as a "tester"? How do you feel about companies using this term in actual job titles? For example QA Tester, Software Tester, and my all time favorite Automation Tester.

That last one really is the icing on the cake. I thought the "tester" in any automation initiative was a Personal Computer or a server? Since when do we need an Automation Tester? Is this person testing the automation tests? I must admit, I am baffled by this one.

Playing devil's advocate, I posted a similar question on a few user groups and lists. The general consensus i received was that the word "tester" as a title is really not a good fit. Unless of course the sole function of this person is to test. In which case it is fitting. But other than that, "testing" is only one aspect of QA as well as just one function (out of many) that a QA / Test team member must perform.

This is not the case in most situations, however, and all personnel in the Quality Assurance department get labeled "tester" by association. Just the fact that they are a part of the QA department makes them a "tester". To me this is just one more proof that we are not doing a good enough job at getting the word out on what a person in our profession actually does.

How do you feel about being called a "tester" by association?

No comments:

Post a Comment

Creative Commons License
VGP-Miami Web and Mobile Automation Blog by Alfred Vega is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.