7 Software Testing Myths
Anthony Mathenge 16th June 2016

Myth 1: It is the QA team’s mistake that the defect was missed.


Reality: Whenever a defect is missed the QA are assured to get blamed. Most of the times the development and other phases run long and QA never gets enough time to test with the rush to release. It makes no sense to expect the testing team to test all possible scenarios in the short period with allocated resources.

Everyone is equally responsible for the defect being missed. The factors like changing and poor requirements, insufficient time for testing, aggressive schedule, last minute changes, lack of resources, lack of project management etc may also be the reasons for the defect being missed.This myth is still believed by many stakeholders and even testers themselves. Many testers do not realize what their role is and blame themselves for a missed bug.


Myth 2: Testing is easy and anyone can test software.


Several people assume that testing is an easy job as there is no/less coding involved and anyone can be a tester.

Reality: Software testing is a challenging job it demands traits like understanding testing methodologies, creativity, problem solving, planning, eye to detail, patience, communication and lot more. It is never easy to come up with scenarios to break the system.

This myth is still deep-rooted in the minds of people. You often see the developers who failed to deliver or the freshers with no formal training being pushed to testing by the management assuming that anyone can test. Software testing is a passion and everyone cannot excel in it. It’s our responsibility as a tester to convince the management that they are wrong.


Myth 3: Testing team alone is responsible for assuring quality.


Reality: The objectives of testing include finding and preventing defects, gaining confidence on the system under test, providing information related to app quality to the stakeholders so that they can decide whether to have a release or not.

Quality is not solely the responsibility of the QA. Quality is everyone’s responsibility. Quality is a development issue, not a testing issue. Developers need to be accountable for the quality of code they write.Testing provides information regarding the quality. Testing process cannot improve the quality unless the bugs reported are fixed.


Myth 4: We can test everything and we can have a 100% bug free software after testing.


Reality: “Exhaustive testing is impossible” this is the one of the basic principles of testing. Testing all the input combinations and preconditions is not feasible. The bugs will remain in the software even after the testing is done. Testing can show the presence of defects but cannot prove that there are no defects. Even if testing cannot find bugs it’s not the proof that the software is bug-free. As a tester one can focus his tests and uncover the defects based on project risks, priorities and project constraints (like time, budget).


Myth 5: Test Automation will replace manual testers and we can automate everything.


Reality: Automation tools are available to assist manual testers to automate their repeated tests and not to replace them. Everything cannot be automated. Automation is not feasible when the requirements are changing and it’s never wise to automate the feature that needs human intelligence and intuition. An automation tool cannot tell if the look and feel is good, if the app is usable etc


Myth 6: Developers need not have to test, there are QA to catch bugs.


Reality: Developers need to perform tests on their code to make sure that it’s functional and ensure that they have created a quality feature. Developers usually perform unit test and integration tests to ensure that their module is working independently and when integrated. Several issues that are caught in unit tests may never be found when tested manually. Developers ideally need to perform functional sanity tests before deploying the build to QA.

These days quality of the product directly effects the brands reputation. The users will get negative opinion on the brand itself if their app or website performs poorly. So no one is ready to compromise on quality. Organizations are always looking forward to work with energetic testers.