Software Testing: When To Go For Automation? Implementing automation could be actually much easier, the real difficult question to answer is: When To Go For Automation? Once you answer it, the rest of the things could be much easier. So, let's see some pointers leading to this. This will help you to answer the above question. Software testing classes in Pune would help you with testing automation and related tools as well. Here are the golden rules on when to go for automation: 1. You are testing a web application where there may be a great many users interfacing with your application all the while. In what capacity will you test such a web application? In what capacity will you create those numerous users manually and all the while? Well, extremely troublesome undertaking if done manually. - Automate load testing to create n number of virtual users to test the load capacity of your application. 2. Some new releases are lined up and bug fixes in the working module. So by what means will you guarantee that the new bug fixes have not been introduced any new bug in prior working functionality? You are required to test the past functionality as well. So, whether you test manually the total module functionality each time you have some bug fixes or new functionality expansion? Well, you may do it manually however then you are not doing testing adequately and effectively. Effective as far as organization cost is concerned, assets, Time and so forth. Here comes the need of automation. - In case of a lot of regression testing, go for automation. 3. You are testing an application where code is bound to change as often as possible. You have practically same GUI however functional changes are all the more so testing rework is more. - Consider automation when your application GUI is almost final but a lot of functional changes are due. 4. Considering 100% automation: It would be ideal if you quit dreaming. You can't 100% automate your testing work. Definitely you have areas like regression testing, performance testing where you can have chance of coming close to 100% automation. Areas such as User interface, documentation, installation, recovery and compatibility where testing must be carried out manually. 5. Will the automation suite have a long life? Each automation script suite ought to have enough life time that its building expense ought to be unquestionably not as much as that of manual execution cost. This is bit hard to analyze the effective cost of every automation script suite. Roughly your automation suite ought to be utilized or run no less than 15 to 20 times for separate builds (General supposition. relies on particular application
complexity) to have great ROI. 6. Avoid automating tests that run once: Recognize application areas and test cases that may be running once and excluded in the regression phase. Abstain from automating such modules or test cases. Testing courses in Pune would provide training in the testing domain. Automation testing is the most ideal approach to fulfill the greater part of the testing objectives and successful utilization of assets and time. However, you ought to be careful before picking the automation tool. Make sure to have skilled staff before choosing to automate your testing work. Generally your tool will stay on the shelf giving you no ROI. Giving over the costly automation tools to unskilled employees will prompt frustration. Before buying the automation tools ensure that the tool is a best fit to your necessities. You can't have the tool that will 100% match with your requirements. So discover the limitations of the tool that is best match with your requirements and after that use manual testing techniques to overcome those testing tool constraints. Open source tool like Selenium, Cucumber is likewise a decent choice to begin with your automation. To get trained on popular automation tools like Selenium or QTP, look for software training institutes in Pune.