1. Evaluate the feasiblity of the tool with your application(support to your tech and extensibility available)
2. Any configuration clashes between your app and the tool.
3. Perform a POC involving a critical workflow and verify the tool capabilities.
4. Ofcourse the cost of the tool and the resource ability.
5. Support avalible in case of any bottlenecks.
6. verify with the vendor on any compatibility issues, if yes then identify possible workarounds.
These are some which you may have to look in , obviously there may be a number of business reasons also especailly with QTP..
Sure the forum members will add..
But you could well search here for more info it may be there somewhere..
1. Its not that i am evaluating automation tools to automate any testing activity. Rather, my requirement is to evaluate an application under test to see whether it is feasible to test it using QTP or not? Here, my automation tool is fixed, that's QTP. Hence i am looking for the areas that i should assess while evaluating an application for feasibility of automation using QTP? Please suggest.
2. I have tried searching the forum for related posts, but failed.
If you already have QTP (licensed or eval), you should try to record and replay some of the important functional flows of you application.
This will allow you to see:
1. If most of the objects in you application are recognized by QTP.
2. If the flows in your application are automatable by QTP or not. (for example, if your application functionality involves frequent restarting of system it is not recommended for automation)
With Warm Regards,
You can easily judge the character of others by how they treat those who can do nothing for them or to them.