Testing Tool Help
The company I work for has just taken on a new multi million pound system to replace an old legacy system. The problem we face now is sorting out a proper testing tool. A problem we faced before is we purchased QARun from Compuware, not long before they replaced it, so we ended up with a tool which wasn't supported, and slowly became unusable. The company we're buying the new system from recommend HP QTP/UFT, but we'd like to do our own research first. If I outline what we're looking for we'd appreciate any advice. Searching online for testing tools brings up so many web pages, forums etc, lots of conflicting information, so I thought I'd try here as you guys helped me overcome some QARun issues a good few years ago
Anyway, below is what we'd like in/from a tool:
Availability of a demo
Ability to handle data driven tests (CSV etc)
Ability to program logic into the test cases.
Active support forums
How is the storage of automation scripts handled?
Is other software needed to support the application? (an example being QTP with QC etc).
Application support from the company.
Creation of data maps through integration with our databases
Smooth and clear UI
Speed compared with other tools
Flexibility in the programming languages that are able to be used when developing scripts.
How future proof is the product
Is the source code available for editing? Ambitious maybe but worth asking
Learning curve – can it be picked up and test fired within 5 minutes, without RTFM....
I know it's a big ask, but as a lot of money is being and will be spent, we want to get it right.
I realised I was asking a lot in my initial request for advice. Scrap the list of requirements, and could you just tell me what tool(s) you use/have used, and if you have any recommendations.
From my experience, just finding the tool that supports your UI is 1/2 the battle.
You'll want walk through the app with the developers. Note all the custom controls, 3rd party controls, and any potentially difficult controls to work with (like grids and data tables tend to be annoying where as simple buttons and textfields tend to be easy)
That'll narrow down a lot of tools.
From there, you'll want to weed out tools that don't have easy extensibility. For example, if a tool doesn't have an API of Appkit for developing your own extensions, throw that tool out. There's a good chance over the lifetime of the app a custom developer control is created, and you'll need to create a custom hook or proxy for it. It's good if you can create support for more object types.
From there, then you can evaluate your other criteria. Since most framework functionality could be either found open source or built yourself. Where as object recognition and extensibility issues will stop you in your tracks.
We currently use WinTask, a bit of Selenium, and a few home-grown tools.
This might help give you an idea what I look for when choosing a tool:
All Things Quality: Things I Like to Have in my Test Automation Suites
Thank you so much guys. We have a meeting today to go through some stuff, so I'll let you know how we get on. Again, thanks for the info, Joe I now have your site bookmarked, and dlai, we've added your extensibility criteria to our manifesto.