What Kind of Tester Are You?

By Lavanya Sukumar | Dec 18, 2017

Quality Assurance testing is a very interesting and important part of agile technology. Are you already a QA tester or thinking of becoming one? You need to possess the following traits and skills:

  • Passion! – This is very important for any field of work, but testing requires complete dedication and passion. In many situations, testers are expected to test the same application several times which means the same test scripts need to be repeated over and over again. To do this with enough patience and commitment, you’ll need to have passion towards testing.

  • Basic knowledge about different types of testing and test standards – This is very important as one has to have an idea about the various testing techniques that are required for an engagement.

  • Defect writing and classification skills – You may assume that it could be very easy writing a defect, but in reality, it is not. Writing a defect with adequate cause and impact to convince the developer along with the sufficient artifacts that will help reproduce the defect is a skill on its own.

  • Test script writing skills – This is another very important aspect of testing. Every tester should know how to write short and precise test scripts that cover both the positive and negative test scenarios with adequate test samples.

In addition, having certain personality traits and skills can make you more apt to becoming a QA tester. People who have an aptitude to become a QA tester are those who are good at multitasking, time management, understanding the engagement from the client’s point of view, and most importantly, have a high attention to detail.

There are many different types of QA testers across the software industry. The key to success depends on what type of tester you prefer to be.

Here are a few types:

  1. Talkative – A talkative tester can be described as someone who solely cares only for the user experience and the performance of the application. You may be a talkative tester if you are always chatting with people to obtain feedback on these two aspects. Also, you identify bugs based on the application’s first impression and constantly evaluate the ease of use and how popular it is among users.
  2. Technophile – A technophile is a tester who is fascinated by test automation tools and always tries to implement such tools for both testing and the test processes. Using these tools, a technophile automates all of his or her test cases to save test efforts and handles several projects simultaneously.
  3. Textual – A textual tester is someone who goes by the textbook. Textual testers always adhere to checklists, frameworks, templates, etc. and is never a fan of monkey testing. To the typical textual tester, everything should follow the standard and guidelines and deviations are never acceptable.
  4. Tedious – A tedious tester believes that end-to-end testing is the road to success. You may be a tedious tester if you don’t believe in shortcuts or quick ‘relevant testing’ techniques that may be required during a time crunch. Under any situation, this tester always demands the sufficient time required to ensure that he or she completes all the types of testing that had been planned during the project kickoff.
  5. Touristic – A touristic tester is someone who believes in exploratory testing and does not adhere to any specific guidelines or standards. You go above and beyond the regular test scripts and always look for edge cases and unique scenarios that may cause the application to fail. The touristic tester does not concentrate on the redundant and repetitive test cases. Instead, he or she finds specific negative test cases that can be used to find bugs in the application.

What would you like to be?

The Total Package!

Any good tester should be a combination of all of the above personalities in order for him or her to adapt to the agile nature of any engagement. This will also ensure that an overall test coverage is obtained. In order to combine these characteristics, we need to modify and accommodate our test strategies based on timelines, cost, the nature of the client, and the complexity of the application. By doing so, we will deliver a high quality application.

mobile_testing

Let's Talk :)