SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Page 1 of 2 12 LastLast
Results 1 to 10 of 16
  1. #1
    Junior Member
    Join Date
    Aug 2003
    Location
    USA
    Posts
    2
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Drawbacks of Winrunner

    Hi

    Can somoene please tell me what are the drawbacks of Winrunner, when can I not use Winrunner. Please email it to me at cis374@yahoo.com
    CIS

  2. #2
    Member
    Join Date
    Jun 2003
    Location
    Brisbane
    Posts
    70
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    a) it doesnt support .net
    b) it uses a proprietary language (TSL
    c) Its difficult to write win runner scripts for non technical ppl (non-prog background)

  3. #3
    Senior Member
    Join Date
    Oct 2002
    Location
    New Zealand
    Posts
    749
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    Additionally:
    d) never use it as a record/replay GUI test tool (a lot of work, high maintenance, minimal payback)
    e) using it any other way requires a sound and applicable Test Strategy, your test collateral has to be of suitable structure, content etc etc
    f) never hope to use it as a fill-in task for people doing other work. It is a full time specialist task - virtually a parallel development project
    g) Do not use screen capture/compare to check results. Do make sure your automated test cases CHECK results - not just run through OK.
    h) depending on the test framework you select:
    1. It can be used to automate and extend regression testing
    2. It can be used to extend boundary testing
    3. It can be used for smoke testing.
    4. It can be used to prepare test cases BEFORE code is delivered (or even written).
    5. It does not remove the need for planning, thinking, or running manual tests.
    6. It is not the tool for Load/Stress/Scalability testing.

  4. #4
    Moderator
    Join Date
    Apr 2001
    Location
    Atlanta, GA, USA
    Posts
    2,167
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    2 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    Item 'a' is not so much of a drawback as it is something that WR is not designed for. QuickTest Pro is Mercury's tool for the .Net environment.

    I'll also disagree with item 'c'. I did not have a programming backgroun when I started using WinRunner and I picked it up pretty quick. Non-technical people? They shouldn't be messing with automated tools at a scripting level anyway (an automation framework designed for non-techs like Celerity, that's another story--they won't use WR at the scripting level).

    Items 'd' and 'e' are true for ANY automation tool. You should never rely on an automated tool's record and playback functionality as it's main usage point. Granted, it's a viable way to learn the tool. I used rec/pb to learn what functions WR used to do certain things. Now I type them out... it's faster. Then I customize.

    Items 'f', 'g', and 'h' are not drawbacks either, they are truths about automated testing in general.

    Drawbacks of WinRunner come up when WinRunner is not suitable for *your* environment. How do you know when that may be the case? Try it? If you're in the evaluation stage, have Mercury do a proof of concept for you. Have them give you an evaluation copy and use the tool in your enviornment.
    Jordan Gottlieb
    Senior Consultant, Orasi Software
    Twitter: @JG_QA

  5. #5
    Senior Member
    Join Date
    Jan 2003
    Posts
    1,898
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    I agree with both c and d specifically for WinRunner. Non-technical people "mess with automated tools at a scripting level" all the time. Allowance has to be made for staff that have those backgrounds. Mercury, in particular, is not the way to go if your staff are not technical. Both QARun (Compuware) and Robot (Rational) are better choices in those cases.

    I would like to add a point i and j:

    I would not try to use either TestDirector or WinRunner to manage an application with >5000 scripts. The only problems I've really had with Mercury surface when I have >5000 scripts to manage. The only way to do it effectively is to break it down into separate projects and that makes the defect manager and metric-gathering processes less effective.

    I am not able to rely on WinRunner (or Test Director) for reporting. Their reporting facilities are notoriously bad. You'll have to customize something and it will require some programming skills in order to do so.

    With all of the points made in this thread, I would like to say that I have, in general, found WinRunner to be an effective tool. In fact, I've found that all of the top 5 tools are effective as long as they are implemented intelligently.
    Every tool has some drawbacks.

    - Linda

  6. #6
    Junior Member
    Join Date
    Sep 2002
    Location
    London,UK
    Posts
    3
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    WinRunner not supporting .Net is a definitely drawback if you have purchased licenses and have to re-purchase QuickTest!

    In addition WinRunner is not suitable if:

    You require to perform your automation via a Citrix ICA client, Terminal Server Client, Remote Desktop Client or any kind of remote control system.

    Your application has complex in-house written or unsupported Windows controls.

  7. #7
    Senior Member
    Join Date
    Jan 2003
    Posts
    1,898
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    rbass,

    I can't tell you how timely your comments were. I have a Citrix-based application coming up to test in a few months (I haven't used it before), and this client uses Mercury products.

    I will plan the testing accordingly...

    Thanks!!

    - Linda

  8. #8
    Moderator JakeBrake's Avatar
    Join Date
    Dec 2000
    Location
    St. Louis - Year 2025
    Posts
    15,609
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    Originally posted by rbass:
    WinRunner not supporting .Net is a definitely drawback if you have purchased licenses and have to re-purchase QuickTest!

    In addition WinRunner is not suitable if:

    You require to perform your automation via a Citrix ICA client, Terminal Server Client, Remote Desktop Client or any kind of remote control system.

    Your application has complex in-house written or unsupported Windows controls.
    <font size="2" face="Verdana, Arial, Helvetica">I have used WinRunner effectively with both Citrix ICA client and Terminal Server Client. I found WRunner very suitable.

  9. #9
    Moderator
    Join Date
    Apr 2001
    Location
    Atlanta, GA, USA
    Posts
    2,167
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    2 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    rbass says:
    WinRunner not supporting .Net is a definitely drawback if you have purchased licenses and have to re-purchase QuickTest!
    <font size="2" face="Verdana, Arial, Helvetica">That depends. Talk to your rep about trading in your licences. There is a cost differential because there is a difference between the cost of WR and QTP, but you may end up where you would have been anyway.
    Jordan Gottlieb
    Senior Consultant, Orasi Software
    Twitter: @JG_QA

  10. #10
    Senior Member
    Join Date
    Jan 2003
    Posts
    1,898
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Drawbacks of Winrunner

    Well, one yea and one nay for using it with CITRIX ICA; guess I'll try it myself and find out, with a backup "B" plan in case I have problems. It is still nice to know (in advance) that there may be difficulties; usually I find out during the process itself, which is messy.

    - Linda

 

 
Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 9.38%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 03:58 AM.

Copyright BetaSoft Inc.