Results 1 to 3 of 3
  1. #1

    WinRunner vs QTP on 16-bit app

    I had a 16-bit app that needed automation. When I tried to automate the app with QTP it just stalled and when I tried it with WinRunner it went just fine. I was wondering if anyone has any facts that would support my finding in my case which that WinRunner was a better automation tool for the 16-bit app.

  2. #2

    Re: WinRunner vs QTP on 16-bit app

    your best facts would be to go thorugh the documentation and see what the supported application bit-levels which are stated.

    The issue comes down to even though you have done a simple test, you haven't truely found out that WR will do all that you need; and personal experiences vary by milage. Every application is going to be different, so what other might have had with success or failure on 16-bit apps in the past probably won't correlate to your situation.

    Going through the supplied documentaiton for WR, and doing further testing on your application with WR will prove out if it is the correct tool for your app or not.
    Insanity: doing the same thing over and over again and expecting different results

  3. #3

    Re: WinRunner vs QTP on 16-bit app

    QTP does not support 16-bit apps (response from then MI), we chose to use QTP on a vb application(16-bit) and had quite a number of problems with the same.

    Many objects were not recognosed and had to have work arounds for them. dont know abt WR though...
    -- Here to Learn and share ---



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
BetaSoft Inc.
All times are GMT -8. The time now is 04:05 PM.

Copyright BetaSoft Inc.