Quality Quotient of a Tester: 22 Core Strengths to Be a Good Tester

This tutorial gives you a list of characteristic features that any tester must possess to become a good tester. And these features, in turn, help a lot in determining the Quality Quotient of a Tester.

Why am I talking ONLY about a Tester? And Why not a Developer or any other role?

I just feel that all the work involved in SDLC in delivering a software is quite simple when compared to the responsibility of a Tester. 

The developer’s scope of work is very well defined within a framework, whereas there is no boundary to the effort spent, value added to the customer and the scope of the work done by the tester.

Tester’s ability, efficiency, and focus are directly reflected in the product behavior during the production.

So, what does it take for anyone to become a ‘Good Software Tester’?

Please note that I do not have any intention to consider the Developer’s or anyone’s work as low or less important in a project. But I’m just taking it as a reference.

Quality Quotient

Quality Quotient of a Tester

Disclaimer: This is a detailed write-up covering all the aspects of the topic. So sit back, relax, and have a cup of coffee to read this :)

All the roles except that of a Tester, are related to the external skill available in the market and they need to learn and utilize it in carrying out their part of their work in software development. But for a Tester, it is the individual characteristics of ability and thoughtfulness that one should possess.

I mean, that one can be a Developer by just learning a coding language. But a Tester just cannot learn one technology or tool or acquire a domain knowledge and say ‘Hey, I’ve learned Python or Selenium or Security Testing in the Finance domain or FMCG domain and now I’m a good Tester’. Hence, learning never ends for a Tester.

As a Developer, one can simply start coding with the coding knowledge that he has, but a Tester cannot just start his testing unless he possesses certain skills. Hence, unless and until he possesses those skills he cannot be efficient in his testing work.

A tester must have worked in a particular technical field or domain along with the tool that is being used for that particular project in his/her previous assignment. But it will not be the same in the next assignment. It would be something else. It would be quite new, a new technology, a new tool, and extremely a new methodology.

Over the period of time, it has been proven that Testers have always been able to pick up the required domain knowledge that is specific to the project, the tools and technology that is being used in the project, and that too within the stipulated time and have been able to carry out testing efficiently and deliver the software as well.

Good Tester:

People generally keep asking ‘What are the qualities of a good Tester?? How can I become a good Tester’?? How can I showcase that I’m a good Tester??

It is not just based on the Testing Methodology, Test design process, Test Execution, Automation or Performance Testing, but a Tester needs to know about all to make him/her a good Tester.

It is the basic culture or qualities that one should possess, which in turn would be strengthened by these external learning, and thereby would make a person a strong and a good Tester.

People are also interested in knowing, ‘What makes you feel better a Tester?’, What do you fetch from the Testing profession? Well, it is nothing but the satisfaction of achieving quality, perfection, neatness, etc., ensuring that you have done some good for your customer.

I’m not just going to talk about these project-specific technical skills that one should possess to be a good Tester. Possessing these skills and knowledge is a must and that alone does not make an individual as an expert Tester, but it will just make him/her one among the group of Testers those who can understand the project basics and carry out the testing.

Hence, rather than just learning, certain qualities or characteristics should be built in within an individual to become a good Tester. And of course it is something that one cannot learn or get certified on these qualities from the available Institutes but one should possess by himself naturally. And later these qualities will be strengthened with more experiences.

So, what do you think that I’m trying to write about now?

I’m going to mention about certain personality traits which I call as the ‘Core Strength’ to be a good Tester.

According to me, whatever skills you add to yourself like testing technologies, processes, tools, and whatever certifications like ISTQB, CSM, Agile Tester, etc, that you attach to your name, can never transform you to become a better Tester unless you have all of the core values which are explained below.

‘Core Strengths’ to be a Good Tester

#1) Being Passionate about the work that we are doing:

The first and foremost important characteristic that one should possess to be a great Tester is to be Passionate about the work that we are doing. I wonder how many of them among the Testers have chosen their role, career, the profession as a Tester by choice??

Unless one has the passion towards Testing, he/she cannot find motivation definitely on a day to day basis to do the repetitive work, again and again, irrespective of the project, technology, complexity and the people involved. Passion is a characteristic, which will make a Tester to explore more and more in identifying the software issues.

Passion is the only thing that will make him/her never contented with the knowledge that they have and the amount of work that they have done and hence it makes them do or learn more and more every time.

I think this can be the best comparison that I can give. It is like a Doctor’s profession. It is not that everyone who has scored high in subjects and got top ranking can get into the field of Medicine. It is the passion that will make one get into this profession.

Imagine how critical it would be for the patients if someone who doesn’t have a passion or a desire for a Doctor’s job, gets into that profession? Similarly until and unless one has a passion for testing, he/she cannot be a good Tester.

I will give you an example which exhibits the passion for the work they do. What else can be better than a self-experience?

The Example may be weird, but it is worth mentioning. And definitely, we should learn from our day to happenings from our surroundings. Observing and learning from each and every small thing that happens in our life is also the quality of a Tester.

As soon as I wake up early in the morning, I go to the balcony to do yoga. Every day I see an old lady, early in the morning rushing in a hurry by keeping long-distance footsteps (I mean walking fast), with her saree tied high pulling from down. Every day I see her with the same rush and the same posture of Saree tied up.

Later I found that she is a housemaid, who washes clothes and cleans utensils for 3-4 houses in that lane. What I observed in her is the passion that she has towards her work. She never misses her work even a single day, she never misses her timing. Imagine her passion and preparedness for the work that she is going for.

While walking on the street itself, even before reaching her work spot, she sets herself to start her washing and cleaning work with her saree tied up. I really like the passion that she has towards her job. Don’t you think passion awakes her every day early in the morning to go to work?

Love my job

I have another Example that will explain the absence of passion on the work. This is when one is made to pick up the profession without any desire and passion for it.

One of my friends became a doctor because of the pressure from his family. In order to maintain his family status, he took up the Medical profession and with a lot of struggle he completed his Medical degree too.

When he started his medical practicing, he never had any passion to do that work on a daily basis and found it very boring after a while. But he was very much interested in doing business. Though he struggled (and also patients) for some time juggling in that profession, he could not continue it for a longer period, later he left it and switched towards doing a business, which was his passion.

Now he is doing very well and is quite happy as well. So, unless one has the passion for their work, they cannot give out their best.

I would say that, in order to carry out testing, especially a quality testing, one should definitely have passion towards the profession and the job that they do on a daily basis.

How Passionate Tester are You?

Passion for Testing and attitude for quality should get into the Testers nerves, their blood, and into their DNA too. Passion for Excellence is what will make an individual, a strong Tester.

Passion keeps one awake always and keeps his eye wide open for details. Passion keeps them active and engaged. Passion for testing makes the Tester to get into the testing mode wherever they go and whatever they see, which in turn is much essential for their role.

#2)  Being creative & innovative:

Being creative & Innovative which is commonly termed as ‘thinking out of the box’ is another important personality trait that a Tester should possess.

Out of box thinking

What is the purpose of testing if one just does the testing of whatever is coded? How will one get a qualitative defect, if he/she just tests whatever has been taken care already?

So, it is this character of creativity & innovative thinking that makes a Tester to think out of the box and gather ideas to design the vivid tests and scenarios, that generally may not have been covered while coding.

It is the creativity which helps the Tester to provide feedback about the product enhancement and helps the product to grab a better position in the market by standing out among the other similar products.

A tester should be able to think and visualize the product just with the details provided through the requirements and hence they should be quite creative and also be able to rip the product by identifying the gaps in the product and showcase how effectively their product can be used and even prove it by identifying the ways to misuse it.

It is the innovative idea of the Tester to best utilize the combination of various tools and technologies available in the market to customize their requirements, in order to achieve the Test objectives by reducing the cost and thereby increasing the speed to the market along with the quality aspects.

With the change in the scope of a Tester’s role, the responsibility of the Tester is not just to find the defect but also to add value to the product, add value to the customer and his business. So in order to do this one needs to be quite innovative, creative, always think out of the box and think unique too.

A tester should be able to think something beyond the level of thinking of an ordinary person. Must go beyond the point of common thinking, imagine various possible scenarios that can occur in reality, and pose questions to themselves like what if it is like this ? and what if that is the case? etc., based on the situation.

#3) Ability to put yourself in customer’s position:

Next important aspect of a Tester’s role is the ability to ‘put themselves in the customer’s position’.

I know it is very easy to say, but really quite difficult to experience the feelings and happenings by being on someone else’s situation, especially the role played as an end user or a customer.

Standing in the customer’s shoe, thinking how a customer would use the product developed by us in their real life, and to understand their expectations as an end customer is a quite challenging one.

One cannot just understand what is running through their mind. It is always common to feel that our product, our creation, our contribution and our work is good to oneself and difficult to find faults within. Hence in order to visualize if our software is meeting the customer’s expectation, thinking in their line of thoughts and doing a role play as a customer is very important for a Tester.

Aspect of tester role

Always thinking about the customer, thinking if I can really test it in the way similar to how customers are using it in real life is the biggest task for the Testers and simulating similar scenarios is the best one for a good Tester.

There could be different types of users from different geographies and different kind of profiles who would engage in using our product and in such cases using ‘persona based testing’ technique is the best option to simulate the customer’s behavior and hence the goal would be to ensure that the end user perspective is tested.

It is always essential to think of various real-time scenarios and relate our testing in Lab with the day to day happenings, and possibilities based on the geography and various personas, and we call it as a ‘Scenario-based testing’ and ‘Use case based testing’.

Hence, it is essential for a Tester to interact with the end user and collect as many scenarios, and use cases as possible to incorporate in their testing.

#4) Visualizing skill:

A Tester should always have a very good visualizing skill.

A tester needs to visualize the end state of the product which is not created, during its development itself. He/she needs to visualize the features and start thinking about its behavior in production and how it would be used by the end user and create scenarios based on that.

Thinking tester role

He/she needs to put all the pieces of information gathered from various stakeholders and from various sources together in their mind and create a visualization of the product. Hence, a Tester needs to get the big picture of the product and its roadmap just with his visualization skill.

#5) Analyzing Skills:

It is not just important to have a big picture of the product but it is also essential to get into the minor details of the product and observe carefully, absorb the content and put that information into right use while testing.

Hence, as a Tester, one needs to observe, think and analyze deeply.

#6) Bird’s-eye View:

Eye for detail is another important characteristic of a Tester.

My belief is that unless one gets deeper into the topic and explores more and more things about the product, it is not possible to understand the product thoroughly and carry out a thorough testing and hence ‘eye for details’, is very important for a Tester to dig out all the product gaps and identify the hidden defects.

Eye for detail

I should add ‘Ear for details’ as well and say ‘Eye and Ear for details’.

Eye for detail will also bring more clarity on the subject. Every minute details of the product matter a lot for the customer. If anyone thinks that this is not important and there is no need to pay much attention, then there we go wrong. So, paying attention and giving importance to each and every detail of the product is quite important.

#7) Being suspicious:

When it comes to identifying the flaws or defects or gaps in the product, ‘being suspicious’ (ha..ha..ha..), literally helps any Tester in achieving their goal of testing. I’ve so many instances where while handing over the build to the Tester, the developer would say ‘yeah, the defect has been fixed and it works fine’.

But when a Tester gets into the actual testing, then we could notice that at times, either the defect itself is not fixed, or partially fixed or sometimes it would have given rise to some other defect due to its side effects. Here, I’m not saying that Developers are lying or cheating, but somehow it is like this in many situations.

Hence, as mentioned, the Testers characteristic is to be suspicious and not to believe anything unless they test and prove that it is working fine. So, be suspicious. Never agree or settle for something that is told. Being suspicious and curious will always add value to the product testing and thereby will reflect the best Character of a Tester.

#8) Reasoning and questioning:

Reasoning and questioning is another important character that a Tester should possess in order to prove to be an effective Tester.

Only the one who really understands the topic can ask questions and the one who asks better questions is considered to be intelligent too. Irrespective of that, reasoning and questioning, in this case, enables a Tester to understand if the implementation made by them is the best option or if there any other options that are available.

Reasoning and questioning

Not only that, as mentioned earlier, questioning helps in getting more clarity on the product and also in understanding why that particular solution has been implemented, out of many other available options.

In such a case, a Tester can further extend themselves to think beyond everyone and come out with better and cheaper idea that no one has thought of so far. We also know the ‘five why’s principle of finding the root cause analysis. This will definitely help the Tester to go to the root of the problem and later identify if a similar problem exists in any other area of the product.

Testers should always keep reasoning about anything that they hear in order to understand better and that too in detail. At times even questioning themselves will help a lot. Why should one design like this and why not like this? What is the critical path? What is the optimized solution?

Actually asking questions makes a Tester more knowledgeable. But it is also quite important to exercise care that only right questions are asked at the right forums, otherwise, it will defeat the whole purpose.

A Tester should have the enthusiasm to understand the in and out of the product, beyond the scope of the testing in order to identify the real problems in the product.

Few times, I’ve noticed the Developers or Development Manager dictating the testing group when there is a time crunch, and the team has fixed the critical defect, saying, ‘just run these test cases, it is enough’.

Ask them why? Understand why that particular defect occurred, and what have they done to fix it. Honestly, a good Tester will not sleep peacefully, unless all the doubts are cleared out to the root.

When I say this, I would also like to mention to the Testers that they should never come under the pressure of Developers and Development Managers or anyone else in the team. It is their responsibility to analyze thoroughly and decide what is required to be tested, instead of leaving it to others to dictate Testers.

#9) Guarding the quality:

Obviously, ‘guarding the quality’, is the best and most mandated quality of the Tester.

We know there are a lot of situations that a Tester would come across under the pressure to compromise during testing, either by not providing enough details when questions are asked or cutting down the testing scope, compromising in case of tools etc.

In such cases, it is always better to put your foot down, let what may come and just do the justice to the quality without any compromising.

Guarding the quality’

I’ve observed in few organizations, where everyone neglects the words of the Test Manager or Test group and take their own decisions about testing. But if that decision in any way leads to compromising the quality, as a good Tester, one should never accept that.

So, guarding the quality of the product ultimately becomes the responsibility of the Tester, even though it is conceived and built by the entire team. It looks very simple, but without compromising for quality, is a very difficult task in reality.

At times, it is a practice that, when everything is completed, the team wants to make some last minute changes, which generally affects the overall quality. So, guarding the quality on such last-minute decisions to make changes to the code becomes the responsibility of the Tester.

When we use the word ‘guarding’, it means a lot. It is not just testing the software and finding defects, but ensuring the overall quality of the software at every stage of the product and keenly watching if any incident/ happenings or any other stakeholder’s decisions contribute to compromising of quality and fighting against such decisions throughout.

Going an extra mile to maintain the quality is known as ‘guarding quality’.

#10) Being Aggressive:

Being ‘aggressive’ in making decisions is another characteristic of the Tester.

Having explained the above situations, where the Testers come under the pressure of compromising the testing and are unable to carry out enough testing. I would say that Testers need to be aggressive in putting up their point of views, decisions, in expressing their thoughts, if not, it will be definitely neglected and ultimately result in poor quality of the software.

When a Tester tries to establish that the defect is critical, then no one would like to accept it in the first instance itself. They always want to push it down or call for a triage to decide if it is critical or not. At such a point of time, the Tester needs to be aggressive in putting up their thoughts.

A tester should not have the attitude of surrendering to other’s decisions unless they evaluate the sanctity of the decision.

Many a time, in the urge of delivering or meeting the timeline, stakeholders recommend to cut down the scope of testing and recommend stating that it would be fine to test only a particular area of the software in case of a bug fix, or it is enough only if these test cases are run. It is always good to take the input but should not get influenced by any other’s decision.

Hence Tester needs to be very aggressive while making such decisions.

Whenever the QA group submits their Testing plan and schedule and tries to convey that the time available for them is not sufficient for carrying out testing, then however detailed their plan and estimate is, everyone tries to push it down. So, in such cases, the Tester undergoes a hard push back in carrying out the testing activities comfortably.

In such a scenario, if the QA team can present their points aggressively then there will be a possibility of change in the decisions in the entire team.

#11) Excellent Communication:

Communicating the required information in an effective way is the basic essential quality of a Tester.

A Tester is required to work with various stakeholders across the globe at various stages of SDLC and hence it is essential to express and represent the information precisely, with clarity and without creating any confusion.

We keep hearing that when a defect from life comes back and hits the QA team, everybody starts blaming the QA team, stating ‘why was this simple defect not found out during testing’? It is quite often that the same defect has already been reported earlier and the team has not given enough priority to take it seriously and fix it.

Whose problem is it? QA failing to critically articulate or interpret and project the impact of the defect appropriately to the stakeholders? and not being effective in communicating the severity of the issue and convincing the team?

So, along with communication, it is the ability to articulate things and influence the team to agree to their point of view, which is the important thing that is essential for a Tester.

Excellent Communication

When I say a Tester needs to be good in communication, he or she need not be an English Laureate but should be at least able to clearly and effectively communicate what he/she feels, either verbally or through a written document.

If one cannot bring out the clear meaning of the content in an understandable manner, then the whole purpose of testing or identifying the critical defect and being able to convey that it is quite critical will be defeated.

Communication could be as simple as explaining the defect description, writing the sequence of its occurrence or explaining the team about the roadblock, which the test team is stuck with being unable to proceed. At the same time, a Tester needs to be pretty well aware that poor and ineffective communication will lead to a lot of confusions and result in poor quality.

Generally, Developers do not like showcasing critical bugs in their code, so what matters here is, the ability of a Tester to convey and convince that there is a bug in your code in a tactic way. While conveying the defects to the development team, there should not be a show off of the feeling that, I have found a defect in your work or you have done a mistake’, which in turn will lead to ego issues in the team. This is all required as a good communicator.

So, Conveying any negatives in an objective way so that, no individual goes into the offensive mode by clearly explaining the impact of the situation is quite important. A tester should always keep the interest of the project in mind while conveying anything without highlighting the mistake of an individual.

In this case, we can extend the definition of a communication skill a bit more for a Tester in terms of writing skills as well, where the Tester in a project needs to document certain things with more clarity, like Readme’s, User guides, generating meaningful test summary reports etc.

#12) Expressing Thoughts/Views:

Talking in the group voice heard

Talking in the group and making your voice heard is yet another important characteristic of a Tester.

It could be a review meeting or a technical presentation or as simple as a gathering to convey a decision to the Testers, to call them to work on the weekend or about presenting a project schedule.

In those meetings, a Tester should be able to stand up in the group, present their points clearly and be able to make their voice heard by ensuring that they really understand what it actually takes to test, what are their challenges and what are the consequences if not tested thoroughly and should be able to influence in reversing the decisions.

#13) Hard Working:

One has to be a real ‘hard worker’ in order to be a Tester.

It takes a lot of time and effort for an individual to understand deeply into the subject and unless one is a hard worker, it is difficult to become a good Tester. Hard work aspect of a Tester does not need much explanation.

#14) Excellent Problem-Solving Skills:

Testers should not be just identifying the defects and throwing all the other problems of the project off the wall to the Developers. It is quite important for the Testers to help the entire team in ‘solving the problem’ or at least proposing the possible solutions to the problems.

Problem-Solution

When a QA has problem-solving skills, stakeholders and everybody else in the team would like to look up to them with dignity and importance and will reach out to them to take their suggestions in case of any problems or issues.

So, if a QA starts analyzing the problems and works with the team to solve the problems, the  QA role in the project not only becomes important but quite interesting too.

#15) Continuous Learner:

A tester needs to be a ‘continuous learner’ and should keep themselves updated by constantly learning, the new technologies and happenings around the globe, which in turn will help them to perform the Testing role in a better way and helps them to stand out in the team.

No matter which path one takes, the focus should be to keep learning.

Let it be Functional, nonfunctional testing, automation, Learning a coding language, machine learning, AI-based automation testing, micro-services testing etc., and to learn anything that comes on their way is the Testers way.

This learning helps them to be more creative, innovative and helps in solving the problems and implementing new ideas and solutions. More the knowledge that one possesses, more it helps them in making the right decisions.

Continuous Learning

It is not just learning the new technique or technology or a new process, but also learning from the previous mistakes, not only from their own but from other’s mistakes too. Constantly learning from others, learning from everything that they see, is the best quality of the Tester.

The one who is in the learning mode always thinks and questions himself, what did he learn today from the happenings. And finally it is not just learning that helps, but implementing the learning in practice is what matters in real life.

#16) Being open to the change and flexible:

Being ‘open to the change and being flexible’ is another important characteristic of a Tester.

We know that a change is inevitable and is always for the good only. A tester should be open and tolerable to the changes in the scope, changes in the design (several times), changes in the architecture, changes in the tool, technology or anything else.

Whatever may change, a Tester should accept those changes and adapt themselves quickly to the change and carry out the testing work honestly without any complaints.

Open to change

A tester should be flexible enough to accept the comments from the stakeholders on their area of work, maybe a suggestion provided to improve upon, automation coverage, defect metrics, test results reporting, hosting triage or anything else. They should be open-minded to welcome any sort of change or suggestion and keep constantly learning and improving.

A tester should be open to work with the Development team with patience, in helping them to simulate the defects, in addition to providing lengthy defect descriptions, logs, and screenshots during bug reporting.

#17) Good Team Player:

A Tester has to be a ‘good team player’.

He should be able to constantly work closely with the team, learn from them and also help the others to learn from self. Testers need to work together with the team in identifying the problems in the product, showcasing them to the team in a better way and help them to resolve it quickly.

Being a good team player

A Tester needs to stand for the entire team when a defect or mistake is identified and support every other Tester in all the phases together in a team. As a Tester, any problem or issue should be owned by the entire team instead of blaming one person. As we know, an individual can achieve more in a teamwork than being single.

Hence, the role of a Team player helps a Tester to achieve the better quality as a team.

#18) Maintain Accuracy:

Maintaining ‘thoroughness, accuracy and precision’ in everything that they do is an important character of a Tester.

Total Quality

Unless they possess this character, the Total Quality of a product cannot be ensured and any posh work will never complete the testing and cannot ensure the total quality. Attention to minute details and not neglecting anything is quite important. It is like a school exam, and we do not know what question will come and from where.

Similarly, we do not know from which part the software bugs will come from if we leave it untested.

#19) Collaboration Culture:

Collaboration culture’ is the key buzzword of DevOps.

With the advent of DevOps coming on to the mainstream usage, collaboration with all the stakeholders, especially for a Tester is utmost important in order to keep up themselves on top of the information and the updates. Collaboration helps the Testers to keep themselves on the same page with the other stakeholders in a program.

Collaboration Culture

Collaboration also helps in prioritizing the testing activities and test scenarios based on the interactions, discussions that a Tester would have with the other stakeholders and helps in reducing the testing cost and thereby improving the quality.

#20) Active Listener:

Another important criteria for anyone to be a good Tester is to be a ‘good listener’.

As a Tester, one needs to listen carefully and interpret correctly by listening to others. They need to gather a lot of ideas and knowledge about the product and how it is going to be used in the real-time by simply listening to others.

Good listener image

A tester needs to understand the real problem of the customer, which are implicit and a customer may be finding it difficult to convert it into the project requirements and document them. So, a Tester should be able to read the customer’s mind and understand them thoroughly by listening to them.

#21) Clear Understanding of Responsibilities:

When there is a crucial release and if the test team has been asked to come on the weekend to carry out the final round of testing and everyone has agreed to come. Then accordingly, work allocation is done among them.

Verified user

Imagine suddenly if someone among the one who has agreed to come either delays in starting the work or does not turn up and does not even inform that they cannot come?? Think of the impact of the situation. Schedule along with quality is in a big question mark.

So, as a Tester one should have the clear ‘responsibility for their work and timeliness’ and needs to understand the dependency on them. They need to keep in mind that their work is at the end of the release and stretching it will affect the entire project schedule.

#22) Customer Centric:

Last but priority wise first, is the ‘commitment that a Tester should have towards the customer’ and their interest.

It is always very much important for a Tester to keep the customer in mind and focus towards them during their entire journey of the software delivery. ‘Customer experience’ and ‘customer satisfaction’ should be the key thinking that should always ring in the Testers mind.

Only this thinking and making no compromise on this thinking will make the product a successful one.

Commitment tester

In situations where any compromise has to be made due to any unavoidable circumstance, then it is the responsibility of the Tester to contact the customer, inform them clearly and take their consent on the compromise that is happening.

A tester needs to know, what makes the customer happy and what makes them annoyed. They should clearly understand what their business targets are and where to focus upon in achieving them.

Conclusion

These are the characteristics that become the yardstick for a Tester to be a good Tester and in turn, helps a lot in determining the ‘Quality Quotient’ of a Tester.

With the introduction of Agile and DevOps coming into the mainstream along with the changing roles and responsibilities of a Tester, both the ‘Testers’ and the entire task of Testing itself has been put under scrutiny.

A Tester, along with the responsibility of testing owns various other responsibilities and wears multiple hats and handles multiple roles in a project as a negotiator, problem solver, advisor, decision maker, as an end user, and as a customer as well.

Hence, now it is very clear that Software testing is not just finding the defects but thinking beyond the requirements and hence, whatever qualities one should possess to be a good Tester depend on the ‘core values’ of the Testers even beyond the technical skills that they possess.

If one does not have these core skills/key strengths or ‘Quality Quotient’ within them, then whatever external training or certifications they add to their kitty will not take them anywhere.

About the Author:

This tutorial is an excellent contribution by our STH team member Gayathri S. She is a core ‘Software Tester’ by her profession from the period of introduction of separate Software Testing role in the IT Industry. She is very passionate about testing and in her words, ‘when I started Testing profession, I never knew that Tester should possess all these ‘core skills’ to be a good Tester and luckily over a period of time, with the attitude of constant learning, the profession has transformed me into a ‘Strong Tester’ by increasing my Quality Quotient.

Are you an eminent Tester with the above-mentioned Characteristics? Do you think that we have missed out any unique characteristic that you possess in the above list?

Feel free to express your thoughts and share your experiences in the comments sections below!

9 Comments on “Quality Quotient of a Tester: 22 Core Strengths to Be a Good Tester

  1. Hello this is good article

  2. This is really a comprehensive and useful article for all the testers out there. It gives a great motivation to do our work with sincere dedication. Kudos to the writer.

  3. the content is informative

  4. Thank you for the extra knowledge!

  5. Really one of the best articles that I read later about software testing career and how the tester can be better, really thank you

  6. Good write up! Its a heads ‘up even for an experienced tester to re-evaluate self to perform better than before.

  7. Hi everyone, thanks for your great words…

  8. Its an eye opening for all test engineers. Awesome write up with bundle of characteristics.

  9. Does Kitty refer to something other than a kitten?

    At the bottom they asked if they missed anything. I would say:

    #23 Handling the unknown. Particularly when there are issues that are inconclusive, Intermittent errors, Strange acting software that doesn’t outright fail the test. These little unknown things can be perplexing. It’s often good to follow-up and investigate.

    #24 Cover your bases: Often it’s better to add in a bug in to the system that might not be easily explainable or easily reproducible. So that there is knowledge there in case someone runs in to another related issue.

    #25, Detailed Note taking.
    Adding documentation to issues and bugs that are discovered is very important.
    Not doing this means you’re a bad tester and you should feel bad.

Leave a Comment