The following Myths of software Testing are:
Myth 1-Testing is very expensive
Reality- Sometimes it is believed and said that, pay less for the testing during the software development and we should pay more for the maintenance or may be correction later. Early testing can save both time and cost in many aspects. However reducing the cost without testing may result in improper design of a software application rendering the product useless.
Myth 2-Testing is not Time consuming
Reality- During the SDLC phases, testing is a time-consuming process but worth it. However diagnosing and fixing the errors recognising during the proper testing is a time-consuming but productive activity.
Myth 3-Fully developed products are tested
Reality- There is no doubt that testing depends on the source code but reviewing requirements and developing test cases is independent from the developed code. However iterative or incremental approach as a development life cycle model may reduce the dependency of testing on the fully developed software. Testing the software at early stages saves time and cost of project.
Myth 4-Complete Testing is possible
Reality– It is an issue when the client or tester thinks that complete testing is possible. It is possible that each one the paths are tested by the team but occurrence of complete testing isn’t possible. There might be some scenarios that are not executed by the test team or the client during the software development life cycle and may be executed once the projects have been deployed. The software cannot be tested with all possible values of input and output in practical because of the time constraint. Hence we use standard techniques and methods for testing.
Myth 5-Tested software is Bug-Free
Reality– This is common myth that clients, project managers, and the management team believes. No one can claim with absolute certainty that a software application is 100% bug free even if a tester with superb testing skills has tested the application. The software testing shows the presence of the defects and not their absence.
Myth 6-Missed defects are due to Testers
Reality– It is not the right approach to blame testers for bugs that remain in the application even after testing has been performed. This myth relates to time, cost and requirements for changing the constraints. The test strategy can also end in bugs being missed by the testing team. The testers are most of the times considered as bottlenecks. But the management and team leaders have to take the appropriate initiative to appreciate the effort of testers.
Myth 7- Only the testers are responsible for the quality of product
Reality- it is very common misinterpretation that only testers or the testing team should be responsible for the quality of the product. Testers responsibilities include the identification of bugs to the stake holders and then it is their decision whether it will fix the bug or may release the software. Releasing the software at the time puts more pressure on the testers as they are blamed for any error.
Myth 8- Testers Automation should be used wherever possible to reduce Time.
Reality- It is true that Test automation reduces the testing Time, but it is not possible to start test Automation at any time during software Development. Test Automation will be started when the software has been manually tested and is constant to some extent. Test automation can never be used if requirements will keep changing.
Myth 9-Anyone can Test software Application
Reality-People outside IT industry think and even believe that anyone can test software and testing is not a creative job. However testers know alright that this is often a myth. Thinking alternative scenarios, try to crash software with intent to know potential bugs is not possible for the person who developed it.
Myth 10- Finding bugs is the task of testing team alone
Reality- Finding the bugs in software is a task of the testers but at the same time there are domain experts of the particular software. Developers are not only responsible for the specific component or area that is assigned to them for development, but also test them.