5 Misperceptions in Software Testing

Software testing is more and more popular these days. I’ve seen people doing, talking and thinking software testing a lot. While I do value all differences in the perspectives, I observe 5 common misperceptions in software testing. These misperceptions bug me because they not only make software testing look cheap but also degrade it.

Misperception #1: “Software tester means loser developer”

I had a chance to interview candidates for software tester positions and they often shared that they were trained to be a developer but for some reasons they couldn’t find job as developer, so they chose software testing. They were seeing software testing job as temporary position before continuing following their dream job as software developer. Why so? Well, there are many possibilities. However, it’s probably because they perceive software testing as an easy tedious task and doesn’t require coding skills.

The fact is that software testing and software developing are two different jobs with different skillsets and mindsets. If you are good at developing software, it doesn’t mean that you can become good tester. In other words, if you are a tester, it doesn’t mean you can’t become a software developer.

Misperception #2: “Everyone can do software testing”

misperceptions in software testing 1 Many people perceive that software testing is an easy tedious job. No programming skills are required. What a software tester does is to sit in front of computer, open the application, click here and there to see if the application works. I’ve been in software testing several years and I wish software testing could be that simple. Actually, software testing can be easy to be approached. However, approaching and doing the job and being good at it are different stories. Software testing requires wide range of skills and traits such as passion, creativity, observation, analytical, communication, debating and of course including coding skill. To some extent, software testing can be considered as an art and of course, not everyone can be an artist J

Misperception #3: “Manual testing is outdated. Now is the time of automated test”

misperceptions in software testing2In recent years, automation testing has become a hot topic. You may hear topic discussing about how manual testing is dying and automation testing is a new hero who saving or fixing the software testing world. Job ads are for automation engineers. Automation tool vendors keep promoting about their mighty tools, the tools can do everything or can replace a manual software tester.

Automated test (or I should say automated check) and manual test are two different approaches which are used to solve different problems. While automated test is fit for regression test, repeated tasks, unit tests, manual testing is fit for exploratory test, usability related test, etc. Automated test is becoming more and more powerful and showing its values. However, automated test /automation tool is not designed to replace software testing.

Misperception #4: “Software testing is a cost-center, not a profit-center”

While I don’t see much of this kind of misperception these days, it still exists. I still see many companies are putting focuses on software developers because they believe they are having great developers who can write clean bug-free lines of code. Also, with the concept of “developer builds thing, tester breaks it” make software testing become less helpful. It is correct that software testing is a cost-center. The more we test, the more we cost. However, without software testing, we may have to face sooner or later the bigger cost of re-calling and fixing units shipped to customer, worse the cost to re-building the lost trust of customer to defective products or company reputation.

Software testing is a cost-center but it’s a necessary one.

Misperception #5: “You missed bugs!!!”

misperceptions in software testing 3Yes, this is one of the scariest phrases testers don’t want to hear from their boss. This comes from the misperception that software tester is gatekeeper (or goalkeeper) whose job is to catch all defects from escaping to end-user. Yes, we could catch all defects if we could apply all testing techniques, test approaches, type of tests, etc. And we could have enough time and money to do all that stuffs. No need to say, this is almost an impossible task when putting in the context of software development works these days where release dates are tightened and costs are cut.

Misperceptions in software testing are not necessarily bad things. They are just parts of learning process. We may mis-perceive things when we get along the way with software testing and we also could realize these misperceptions when we have more experience in software testing. The most important thing for testers is never stop learning and sharpen our saws.

[Updated – Nov-21-2015]

I have just created another version of this article and put it on Slideshare. If you like Slideshare format, you can see as below:

Like What You’ve Read?

Subscribe now to be updated on future posts


  1. Aditya

    Great post Thanh.
    Do you have any ideas to avoid missing bugs?

  2. Thanh Huynh

    Thanks Aditya,

    Although bug missing is one of bad sign of not doing good job as tester, missing bugs may happen time to time for many reasons. What best we actually can do is to avoid missing “critical bugs” to mitigate the risk of leaking bugs. I suggests some practices:

    1) Make sure you cover the happy path of main features of the system
    2) Don’t assume things when you’re unclear about somethings.
    3) Start testing early and involve more people to test. The bug will easily escape when there’s only testers as final gate.

    Hope it helps.

  3. AmirShahzad

    6th one . Many people think tester are the responsible for the quality of product or project but they are not .
    because tester job is to verify the requirement not making the quality

  4. Thanh Huynh


    You’re right. Tester is not responsible for the quality of the product. However, there are some test teams claim themselves as gatekeeper and be responsible for quality.

  5. Paul

    Nice article :))

Leave a Reply

Your email address will not be published. Required fields are marked *

© 2024 AskTester

Theme by Anders NorenUp ↑