There are many good reasons to start automation. But sometimes – Companies start automation testing with enthusiasm but end up with manual testing only. Below are 5 mistakes that management might do while implementing automation:
1. “Test automation is the answer to testing problems”. Management says “We have so many tests and so little time, let’s use test automation. It will solve our problems.”
However it’s not true. Implementing/designing scripts by automation tool may take 3 times 100 times longer than the implementation of manual testing scripts. So if your project is at critical and final stage, so starting testing automation might not be a good idea.2. “Development of automation scripts (or automation testing process) cannot be started, as application is not stable yet. Developers are still in progress of developing the application.”
It is not true. Phases of test automation process and software development process are almost same. Automation itself is a development process. As soon as the development activities start, at same time planning of Automation testing should be started. Development of scripts can also be started earlier. You can get access to software (which is under-construction) from development team and start preparing automation scripts. You can get help from low level design documents.

3. “Now our testing team has automation tool. They will develop more tests efficiently.”
Automated tests development is a code development. Are you sure, your test team is trained in this? At least one programmer should be there in the team. Training must be given to the automation team, so that they design better tests.

4. Management (along with Test manager): “A sales executive demonstrated an automation tool to us and it seems that tool will add value to our testing. We think we should buy it.”
Vendor gives demonstration on which application? Is it yours or is it vendor’s application itself? Is tool support the same technology on which your application is developed? How much programming is required to develop tests? (Note – this is directly related to people skills and ROI). Consider Cost to Automate the Tests.

Involve Automation experts/Test architects while purchasing any automation tool.

5. “It has been 3 months and we didn’t see any progress so far.”
How many testers are involved in automation? Are they 100% allocated to automation?
Sometimes, only one automation expert is allocated to the project. Management thought that for automation fewer resources are required. However it is not always true. Also, the automation team should be 100% dedicated to automation project only. They should not be shared in other projects.
In the last, remember – A fool with a tool is always a fool. ~ by Anne Mette Jonassen Hass (Guide to AST)

References – LogiGear.com
Must Read – http://www.softwaretestingtimes.com/2010/04/selecting-software-testing-tool-testing.html


Note – As far as the title is concerned, Brian Marick (@testing.com) wrote a paper on “Classic Testing Mistakes”. So we put the title as “Classic Test Automation Mistakes” [just for fun 🙂]