Common Software Testing Myths

Below are listed the common myths that we encounter in the software testing industry. These myths are statements which are false, but they are so widespread that over a period of time, people assume them to be true.


Myth 1 : A software tester's only task is to find bugs.
This view of the tester's role is very limited and adds no value for the customer. Testers are experts with the system, application, or product under test. Unlike the developers, who are responsible for a specific function or component, the tester understands how the system works as a whole to accomplish customer goals. Testers understand the value added by the product, the impact of the environment on the product's efficiency, and the best ways to get the most out of the product.

Myth 2 : Software Testing is done to demonstrate that there are no errors / bugs /defects in the software product being developed.
Testing is the process of uncovering defects... The objective of any tester should be to try his / her best to crack the code. A tester should never work under the assumption that the system works!! The software product should be tested with the intent of finding errors.

Myth 3 : Software Testing is easy.
Seldom is testing easy. Though it’s simple to prepare straightforward test cases, at times testing can be a real challenging task. Any production issues will, in many cases, backfire first to the testing teams. Why was this scenario not covered in the test plan?? Therefore, a Tester should develop the capability to look or think beyond the requirements mentioned in the test plan or specifications.

Myth 4 : Software Testing does not offer any opportunities for career growth.
There are a wide range of roles that one can take up, if opting for a Testing career. Pursuing a testing career offers more scope for improving Business/Domain knowledge. It enables one to adopt a holistic approach of the entire software system instead of concentrating on just a unit or module. A good number of testing certifications are offered by reputed institutes, which helps you attain a strong foundation in this career path.

Myth 5 : Software Testing is not as complex as development.
Testing is most of the time required to be one step ahead of development. Be it in sizing, efforts or complexity. A developer most often is concerned with a distinct module or unit. Testers are most often aware of the entire system and hence have better system and domain knowledge than a developer. The more complex a product has been developed, the more complex the testing has to be in order to ensure it goes with quality.

Myth 6 : Programming / Development is distinct from Testing.
Testing DOES involve programming. Automation Testing is a separate branch of testing which deals 100% with programming in different languages (C#, Java, Perl, Python, Ruby, VB … ) There are testers who know programming better than developers! Going ahead, automation will become more and more of a necessity.

Myth 7 : Anyone can become tester, they should have ability to read and follow instructions, that’s it.
Anyone can become a tester – TRUE. But not everyone can become a professional Tester. This is one of the most damaging myth of all and to some extent this is because of some of the practices we have seen in our industry. Everything else apart from Manual Scripted Testing, right from test design, to test execution to automation is highly skilled and creative job and can be done effectively, only if you are skilled. Not considering testing as a skilled profession has done more harm to the testing community than any other myth.

Some More Software Testing Myths.

• The tester’s task is easy: he should merely write and execute the test cases by translating requirements to test cases. Additionally log some bugs.
• Test case Reviews are a one-time effort. All you have to do is take an artifact after it is completed, and verify that it is correct. Test case reviews, for example, should merely verify that *all* requirements are covered by test cases and EVERY REQUIREMENT is COVERED by AT LEAST ONE TEST CASE.
• Software Testing should be like manufacturing. Each of us is a robot in an assembly line. Given a certain input, we should be able to come up automatically with the right output. Execute a set of test cases (should execute 100 test cases a day) and report pass/fail status.
• Software Testing has nothing to do with creativity. Creativity – what? The only part which requires creativity is designing your assembly line of test case design. From that point on, everyone should just be obedient.
• Quality is all about serving the customer. Whatever the customer wants, he should get. Things that don’t concern your customer should not be of interest to you.
• Anyone can test and no particular skill set or training is required.
• Testers can test for quality at the end of the development cycle.
• Testers hold up implementation.
• Giving testers less time to test will reduce the chance of them finding defects.
• Letting the testers find the bugs is the appropriate way to debug the system.
• Defects found in the production environment are the testers fault.
• Testers do not need any training, only programmers do.