I've spent a lot of time working with QTP over the years, and have successfully driven tests using a combination of batch processes, VBS processes and QC OTA API calls. While QTP works nicely (has it's niche and so on) I have a personal preference for Selenium WebDriver[0] for integrating testing within an agile team (light weight, cost, versatility of tool, reporting, debugging, targeting tests, ease of writing and updating assets, scaling is actually affordable, actually means working with developers, and so on).
[0] Full list of tools involved in current project's implementation
- Selenium RC/Grid for distributing tests,
- TestNG for driving the tests,
- Subversion for assets,
- Cruise Control at present,
- moving to Jenkins for building all artefacts,
- Python for serving up results, and
- PSExec, VBS and batch scripts for deploying/initiating/plumbing everything that's needed.
No comments:
Post a Comment