Automated testing requires different skills than manual testing. No matter how far along the automated testing tools have come -- and the tools have matured tremendously over the past decade -- automated testing requires programming skills. Tool vendors sometimes state that capture/playback is robust enough to eliminate the need for programming but the claims don't hold up to real life testing needs. I believe the limitations of capture/playback in automation have become widely recognized in the software testing community. Tool vendors persist. My advice is to remain skeptical until proven otherwise. (Isn't this a tester's mentality anyway?)
Now, if you believe that automation requires programming skills -- which I believe -- then the question becomes, are these skills you possess and if not, do you have the technical aptitude to acquire the skills? Some manual testers have the technical aptitude to become automated testers and some do not. If you're someone whose background includes programming knowledge and experience, then the shift to test automation might be fairly easy. You might try automation and see if you have the skills.
Before you convince your company to buy a tool and pay for vendor-specific training, you might start by programming with an open source tool as a trial (and possible solution). Some automation tools are available at no or low cost and you can find information online so that you can experiment in automation without investing in a specific tool. I hear good things about Watir and Selenium but I cannot say more directly since I do not have hands-on experience. Free is a good way to experiment before spending.
I suggest checking the tool meets your needs before purchase. You can request vendors to provide a proof of concept or check the return policy before purchase. Not all tools are designed to work in all technical environments; some tools are geared for specific environments. You might consider building a matrix of comparison to check features and pricing before purchase.
Another word of caution based on my experience, before purchasing a tool make sure you have the staff and skills needed to keep the tool up, running, and in use. Shelf-ware is common problem with automation. Tools get put up on a shelf and fall to disuse when there isn't sufficient staff to continue both manual and automation or sometimes when companies don't want to pay for training. Tools require commitment.
As for Mercury's QTP testing tool, I have worked directly with the tool and had a positive experience. I attended QTP training and had a highly skilled instructor with good experiences to share. All training has some dependency on the strength of the instructor and the student's readiness to learn.
Automation can provide fantastic ways to test a multitude of scenarios and test with volumes of test data that would never be achievable by hand. Testers with automation skills are nearly always in demand but like any job, if you don't enjoy what you're doing, why do it? Best of luck.
Dig Deeper on Automated Software Testing
Related Q&A from Karen N. Johnson
There are so many resources out there about the ever-changing world of Web design and mobile testing, but to choose the most salient and insightful ... Continue Reading
In this expert response, consultant Karen Johnson describes strategies she uses for browser compatibility testing. Experience and knowledge of common... Continue Reading
Initiating test automation on your project team may seem challenging, or even overwhelming. Fortunately, expert Karen Johnson has been through this ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.