There are many myths about testing. Some common myths are as follows:
1. Testing is a very easy task and can be performed by anyone: People other than the tester always think that testing is a very easy task and it can be easily performed by anyone, which is not true. Testing it is not an easy task as because tester always have to create a scenario and think differently. Testers always have a different approach to look through the application.
2. Automation testing can be done at any point of time: Automation testing can always be started once manual testing of the product is done or the product is stable to some extent.
3. Testers task is to find bugs only: Testers find bugs but this is not the only task of the tester. Testers are familiar with the whole flow of an application, like developers who are familiar with the module in which they are working.
4. Automation testing will soon replace the need of the manual testers: It is assumed that in future there will be no use of manual testers as the technology is growing at a very high rate. But this point should not be forgotten that the users of the application will be a human being rather than a machine, hence, manual testing done with tester will be needed.
5. Testing is a time consuming process: Testing is a time consuming but effective process.
6. Testing can be done after the product is fully developed: Testing can be done when the product is completed but creating scenarios and writing test cases is independent from the development of the complete product. One should prefer Agile methodology in which testing and development of the product go side-by-side.
7. Once testing is completed, the product is bug-free: This is a very common myth that everyone related to the product has. It is not possible that a product is 100% bug-free. Even if the skilled tester has tested the product then also it cannot be said that the product is bug-free.
8. Defects in the application are due to the testers: Time, lack of requirements, costs and other features may be the cause of the defect in the application. This is not a correct approach to blame the tester for the defects left in the application.