| || |
QTP VS Silktest
I'm trying to evaluate if QTP is suitable for a product which undergoes huge UI changes frequently. I see that QTP is not that better than silk test various scenarios. But i couldn't analyze on how QTP scripts can be reused if there is an UI change in the product.
Can someone help me with the comments.
Thanks in advance!!
Re: QTP VS Silktest
[ QUOTE ]
But i couldn't analyze on how QTP scripts can be reused if there is an UI change in the product.
[/ QUOTE ]
QTP and Silk are similar in this respect: you would change the GUI Map def (in Silk) or the Object Repository def (in QTP) for the object which changed in the AUT. Or, if you were using Physical Descriptors (in Silk) or Descriptive Programming (in QTP) you would changed you scripted def for the changed object.
Here is a thread that attempts to address diffs between Silk and QTP for those transitioning to QTP from Silk:
Here are two good threads on QTP FAQs that might help in youre evalution:
I am no longer active on the sqaForum's Silk board, but it likely has the equivalent of the above FAQs that you can evaluate as well.
But, in the final analysis, set up a small, but written, head-to-head evaluation plan against a typical AUT in your environment, and then get a 2 week evaluation copy of each tool. Run them through the paces defined in your evaluation plan and then select the one that best meets your needs (neighter tools will do all things "bests").
-Hope this helps, Terry Horwath