I am an experienced scripter in both Mercury QTP and Watir, and I'd have to say
that they are very comparable in functionality. At this time niether QTP nor
Watir have the ability to do a whole lot easily with Firefox or other browsers,
and QTP will never support Safari or linux based systems,
excellent point. The way feature requests are handled, the ability to
extend the functionality of watir yourself and no longer fighting with
a test tool vendor's support are the main advantages of watir over
mercury in my opinion.
and after all you can play with the nice ruby language instead of
Thanks for the great input. I have a more specific question though. How is the
support of (well written) QTP steps down the road?
Watir/Ruby scripts (if well designed) seem to be very easy to support. Is that
also the case with QTP?
On 11/7/06, John Lolis [EMAIL PROTECTED] wrote:
Watir/Ruby scripts (if well designed) seem to be very easy to support. Is
that also the case with QTP?
Don't know about QTP, but I remember Winrunner was laughable. I would
guess if you
are using VBScript JavaScript as your test script languages
Looking for some experience from people that have used both. We are currently
looking into both of these applications, and I'm wondering if anyone has any
experience (that they care to share on the subject).
Cost alone isn't that big of an issue. So its a point that doesn't need to be
On 11/6/06, John Lolis [EMAIL PROTECTED] wrote:
Looking for some experience from people that have used both. We are currently looking into both of these applications, and I'm wondering if anyone has any experience (that they care to share on the subject).
I don't know if it was WinRunner or QTP,
