Software Testing Myths

Below are some of the top Myths of Software testing

Myth: Testing increase development cost.

Reality: Early testing saves cost in all aspect; if the product is not tested properly it may result in product useless due to improper design software application. It also avoids paying more for maintenance or correction latter.

Myth: Testing is waste of time.

Reality: In SDLC phases testing is not waste of time rather it is part of the process.

It is considered as productive activity for finding and fixing the bug/defect which is identified during proper testing.

Myth: Once product fully developed then only testing can be done.

Reality: Testing is independent of development; it starts from reviewing the requirement and preparing the test case. So testing doesn’t need to wait until product is fully developed there are some development life cycle model which are iterative or incremental in approach to reduce testing dependency on the fully developed software.

Myth: It is Possible to do complete testing

Reality: It's not possible to say 100% testing is completed and 100% bugs are fixed. It is possible that all ways have been tested by the team but complete testing is never possible. There may be chances of some scenarios may are never executed by the testers or even by the client during the SDLC and may be executed once the project has been deployed.

Myth: The objective of Testing is to make sure that 100% bug- free product.

Reality: The objective of testing is to ensure to uncover as many bugs as possible. Finding all bugs and getting rid of them is impossible. Testers with super testing skills who has tested the application cannot absolutely say that a software application is 100% bug free. 

Myth: When a defect missed, it is the mistake of the Testers.

Reality: Quality is the responsibility of team, including developers. It is not correct to blame testers for defects that remain, after the application testing has been done.

Myth: Quality of a product is responsible of tester.

Reality: Whole team is responsible for the Quality product. Tester role is to make sure quality is followed in the development of product. Tester’s role involves finding the bug to the product owners and it’s their decision to fix the bug or release the software. At the time of software release more pressure is on the tester for any errors, as they are blamed for it.

Myth: Automated testing eliminates the need for manual testing

Reality: 100% test automation cannot be achieved. Manual Testing, to some activities, is always needed. After completion of manual testing and the software is stable Automation testing can be implemented. If there is frequent change in requirement then automation is not advisable.

Myth: Any one can test a Software application.

Reality: Testing is a rigorous activity and requires various types of skills.

Myth: A tester's task is only to find bugs, there is no creativity

Reality: Tester should have domain knowledge to find bug in particular software. Developer will only work on specific part or area that is assigned to then but testers have the knowledge on overall workings of the software, the dependencies and the impacts analysis of module to module. Formulating test approaches, designing tests, and executing tests are part of creative process.