Items to consider before automating an application

Manual testing is the process of manually testing software for defects. In this Manual method the tester plays an important role as end user and use most of all features of the application to ensure correct behavior.

Automation Testing is a process which is done by the help of automated tools like Selenium, QTP (UFT), Watir, SoapUI, TestComplete, etc. etc. Automation Testing is a continuous part of Manual Testing.

Manual Testing VS Automated Testing

Difference between Manual and Automation Testing is the pillar of Software testing, because whole testing is based on Manual and Automation Testing. In a project you can do either Manual or Automation Testing and you can also do both Manual and Automation Testing simultaneously. Manual Testing is a start of Testing, without this testing we can’t start Automation Testing. Automation Testing is a continuous part of Manual Testing. All the famous phases of STLC like test planning, test deployment, result analysis, test execution, bug tracking and reporting tools are obviously comes under the category of Manual Testing and done successfully by human efforts. In Automation Testing all the popular phases of STLC are done by various open sources and purchased tools like Selenium, J meter, QTP, Load Runner, Win Runner and so on. It takes less time. It takes lot of time. Regression Testing process is easy in Automation Testing by Tools. Regression Testing process is tough in Manual Testing. Few testers are required in Automation Testing because in this testing test cases need to be executed by using Automation Tools. More testers are required in Manual Testing because in this testing test cases need to be executed manually. It gives high accuracy result. It gives low accuracy result. Need of programming is must in Automation Testing. No need of programming in Manual Testing. It is expensive. It is not expensive.

ITEMS TO CONSIDER BEFORE AUTOMATING AN APPLICATION You have some new releases and bug fixes in working module. So how will you ensure that the new bug fixes have not introduced new bug in same and other working modules. You need to test all the modules manually. You might do it manually but then you are not doing testing effectively. Effective in terms of company cost, resources, time etc. Here comes need of Automation. Automate your testing procedure when you have a lot of regression work. You are testing a web application where there might be thousands of users interacting with your application simultaneously. How will you test such a web application? How will you create those many users manually and simultaneously? Well very difficult task if done manually. Automate your load testing work for creating virtual users to check load capacity of your application. You are testing application where code is changing frequently. You have almost same GUI but functional changes are more so testing rework is more. Automate your testing work when your GUI is almost frozen but you have lot of frequently functional changes.

GRAPHICAL ANALYSIS OF MANUAL AND AUTOMATED TESTING

Are you thinking of 100% automation? Please stop dreaming. You cannot 100% automate your testing work. Certainly you have areas like performance testing, regression testing, load/stress testing where you can have chance of reaching near to 100% automation. Areas like User interface, documentation, installation, compatibility and recovery where testing must be done manually.