On 11/6/06, John Lolis <[EMAIL PROTECTED]> wrote:
I don't know if it was WinRunner or QTP, but one telling story from about 18 months ago:
I was giving some training about testing to umm some people. Important people. These people had an application that ran in IE and was full of crazy ActiveX controls. I was going on about how cool Watir was, and one of the people in the session said "we have this one page where WinRunner just crashes. We can't figure out what's causing it."
So we cranked up Watir. Not only did Watir not crash, but using Watir, we were able to identify the exact line that was causing the WinRunner crash.
This particular line was so heinously non-standard that the Mercury tool couldn't even bear the sight of it and crashed. Watir just ignored it. No matter how we tried, we couldn't interact with this heinously non-standard widget.
Of course, somewhere in the bowels of COM or DCOM or COM++ or OLE or something is the key to interacting with that particular widget, but it was only a one-day overview I was teaching, and we didn't pursue the problem any farther.
Although I don't use Watir very much anymore, my favorite part has always been asking for new features. In fact, take some time to go through the mail list archives looking for all of the features that people have requested and received over the past couple of years. It's an impressive list. Try doing that with Mercury.
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, but one telling story from about 18 months ago:
I was giving some training about testing to umm some people. Important people. These people had an application that ran in IE and was full of crazy ActiveX controls. I was going on about how cool Watir was, and one of the people in the session said "we have this one page where WinRunner just crashes. We can't figure out what's causing it."
So we cranked up Watir. Not only did Watir not crash, but using Watir, we were able to identify the exact line that was causing the WinRunner crash.
This particular line was so heinously non-standard that the Mercury tool couldn't even bear the sight of it and crashed. Watir just ignored it. No matter how we tried, we couldn't interact with this heinously non-standard widget.
Of course, somewhere in the bowels of COM or DCOM or COM++ or OLE or something is the key to interacting with that particular widget, but it was only a one-day overview I was teaching, and we didn't pursue the problem any farther.
Although I don't use Watir very much anymore, my favorite part has always been asking for new features. In fact, take some time to go through the mail list archives looking for all of the features that people have requested and received over the past couple of years. It's an impressive list. Try doing that with Mercury.
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
