I have this question asked of me quite frequently. Somehow I will be involved in a discussion and something will come up about testing, and when I talk about it, a natural question to be asked is “oh, so you must be in Quality Assurance!” For years, I answered “yes”, but I don’t answer that way any longer. Now, when people comment that I must be in QA, I answer, “Am I a software tester? Yes!”
For many of the people I talk to, the comment doesn’t just hang in the air; they notice the difference, and often they ask me about it? What do I have against QA? Why do I avoid saying those words, and why do I substitute the words “software testing” instead?
2. These are of course all semantic what they will do with that information. Often it
arguments. The fact is, Quality Assurance is a will be to take the problems that we have found
long established term, and for the most part it is
least in the environments that I work in, we don’t synonymous with being a tester. Still, I prefer leave the issues as is.
have that control or power. We have to have a using the words “software tester” for a variety of Each time I have this conversation, I have
programmer make those changes. Thus, the ability reasons. First, it accurately effects what we do. the chance to change someone’s mind on how
to assure quality is not in our hands. We test the software. Not an idealized piece of they see software development and what we as
The biggest reason, though, has nothing to software on some mythical perfect machine, but
do with these situations I’ve described. The reason opinions; the long-term use of the QA term is
I dislike using the term “Quality Assurance” the on a lake. We look at a product and we explore
most is the false expectation it gives. It tells people it. We discover with the resources at our disposal someone who gets what I’m saying, and they start
that we can assure quality, in a way that says we how the software behaves, and based on that to view software testing differently. I’ve even heard
will prevent any defects from getting to the public. behaviour, we explore in different places. Jon Bach a number of software testers likewise answer in
While yes, that is ultimately what we want to do, has a metaphor that I personally love1, in essence kind when they are asked if they “work in QA?”
the fact is that it is impossible to test completely, saying that instead of trying to present ourselves as It’s going to take time to change perceptions, but if
to examine every conceivable situation, and cover we all work together and remind people what it is
every eventuality to assure that there are no defects. should use something closer to who and what we we really do, we might help others understand that
If a defect does get out, we have set ourselves up really are. We are storytellers. We are journalists. the term Quality Assurance belongs in the factory,
for blame. We are Quality Assurance, our job is to Our goal is to explore, study and learn about a while software testing belongs with the code we
assure the quality of the product, and therefore any product, from as many different vantage points as work with every day.
we can, and then, based on those vantage points,
explain what we see. Tell as complete a story as
that particular issue, neither did the programmer possible. Show the software team and product h i p i h i q r i s
who wrote the module, or the product owner who owners the who, what, where, when and why of the
accepted the module. We’re all on the same team. software. We are providing the development and t
Setting ourselves up to be the judge, jury and product team, and the customers, with information
executioner will merely leave us to be blamed if we
miss something. product team and the programmers will determine
QA Wizard: Intelligent Tools for Testers
QA Wizard Pro Resource Thief
Automated Functional Load Testing Stress Testing
Automate your web, Windows, and Java testing, and gauge With Resource Thief you don't need to maintain virtual
the real-world performance of web sites with QA Wizard Pro. machines, or create crazy configurations in the lab to test
application behavior in stressed environments.
Create adaptable scripts that require less maintenance with
an object-based recording engine and global control repository Limit disk, memory, and network access to specific
applications
Test the latest technologies including HTML 5, Java, .NET,
Qt, AJAX, and more Run existing, or new test cases against the application
under test
Simulate hundreds or even thousands of users to measure
the real-world performance of your web site Use your existing diagnostic, testing, and development
tools during stress tests
Visit www.qawizard.com to learn more and download your free 30-day trial today. Learn More
a
ief
Br
t
HisorY
OF
Time
Fr
enchEdition