Often, Testers use words, phrases without calculating the probability of putting oneself / team / project in trouble by use of such statements.
Testers should be wary of using such phrases and should not believe in them blindfold.
I have prepared a list of such words, phrases that a Tester should avoid using. So here’s the list that may set the bomb:
I have done Complete Testing:
Do you really think its possible to do Complete Testing? Can anyone claim that the software is completely bug free? Have you tested the application in different environments, paths & combinations? Were your findings enough to cover entire testing? Have you considered all the possible scenarios? What about non-functional testing? Security, performance Testing? Different OS, browser combinations? Configuration Testing? Testing on Mobile with unending number of combinations.
My Assumptions are correct:
Do you rely too much on assumptions? Do you have those pre-conceived notions that you believe are universally true to fit and apply in any System? Have you stopped yourself from observing the situation to validate whether your assumptions are correct or not? Not asking questions can only strengthen your assumptions.
Testing is easy:
So you believe testing is no brainer work. This statement makes sense only if you have no questions to ask. If nothing leads to creating doubt in your mind or you do not want to question your beliefs & is without ideas, you are not only establishing the idea of “testing is easy” in your mind, but also, making your customer’s life difficult and your own life hell. Understand, testing should be an idea generating activity.
Testing is without a mission:
Do you test the application without a mission? Do you believe your role of being a QA justifies your mission. Is Testing more of an Obligation? Don’t you believe in adding Value to the System?
Tester should have a mission that defines their plan of action. No mission means no testing without a reason.
I am a Certified Tester:
Do you think having a certificate is enough to qualify your testing skills. Do you define your Success through the number of certifications you carry in your resume? Do you think only a certified tester can only add value? Are skills equal to certificates for you?
What about the biggest skill of self-learning? You learn through your experiences, through the mistakes. Your learning makes you a strong, learned tester. No external recognition like certification can qualify your only learning.
Am good at playing blame games:
How many times you throw the ball of blame at developers, DBAs, System Admins or our sub-ordinates for the issues in production or for not doing the work on time and neglecting it? Do you really introspect yourself and think about the mistakes that could have been avoided in first place instead of getting into a WAR room now with the management and playing the nasty blame game.
Ego … hmmm:
Does your ego play a crucial role in your work? Trust me, it does no good to anyone.
Approach the situation with open mind. Listen to your peers. Discuss ideas with them. Learning through experience and knowledge sharing is the best form of learning. Don’t let your ego stop that process.
All Symptoms are bugs:
Are you in the race of logging the maximum number of bugs to show to the management how competent you other incomparison to other testers? First of all, you may be reporting symptoms which may not be bugs. And secondly, quantity of bugs reported doesn’t matter. What matters is the quality. Imagine someone suffering from high fever, cold, vomits which may be symptoms to a bigger issue at hand – maleria. So doctor thoroughly tests the patient to know the issue she is dealing with. Only then she prescribe the correct medicine.
My experience talks about bug tracking tools:
I see resumes where people add a list of bug tracking tools they’ve worked on. Is that a skill to know a tracking tool? Is tester missing the real testing experience to cover it up with tracking tools experience? It’s like adding in your resume, “i know how to search on Google”.
I follow Best Practices:
Do you think only by applying best practices you can provide solution to the problem at hand. I believe first thing is to explore and understand the situation. Understand the context and based on your logical deductive reasoning, apply the solution. Remember, right hand driving may be a best practice with guaranteed Success results in America but the same practice may not work in India.
I am sure you as a Tester can add many more “words of warning” to this list. I am looking forward to hear from you.