SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 10 of 10
  1. #1
    Senior Member
    Join Date
    Sep 1999
    Location
    San Jose,CA,USA
    Posts
    340
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Winrunner edit commands and a debugger annoyance

    All

    I am picking up winrunner after a 3 year hiatus (yes I am a Silk biggot .. but I have used BOTH). So I was wondering about two fundemental things in the editor, and one in the debugger.

    Thing #1
    Is there a simple way to copy an object identifier from
    the Gui Map into the editor .. I will keep reading the
    docs .. but I don't see it yet. (other than a record)

    Thing #2
    Is there a way to round up french curves and
    parenthsis. For instance
    if (a == b) {
    for (i=1;i<10;i++) {
    for (j=1;j<20;j++) {
    # for shame doc startin a for loop wi out
    # a closing french bracket

    }
    } else {

    }

    In one of my favorite editors you just put your cursor to
    the opening french curve | paren and the ending FC or Paren will be shown via ctrl + b. Anything like that I am eternally screwing up my brackets esp when it gets complex.


    Thing #1 debugger:
    Why when I am stepping through the code via ctrl_L + f8 do I keep getting a VERY annoying record dialog? The whole soft key thing is in my opinion overdone in WinRunner .. is there a practical way of backing this off .. and what shoudl one turn off, with impunity .. or conversly what must one always keep on?
    Smoke me a kipper, I'll be back for breakfast!
    Sincerely
    Richard Weth
    Sr. QA Engineer

  2. #2
    Moderator
    Join Date
    Mar 2000
    Location
    Orange County, CA
    Posts
    3,187
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    Let's see if this helps -

    Thing #1: If you are talking about in the context of creting the CS statements, the only way to link the statement up to the object is via the function generator where you can click on the object to populate the command. If you are doing it manually (typing it in), there really isn't an easy way other than knowing what it is from teh GUI Map and retyping it, or copying the info from one to the other.

    Thing #2: Not in the standard WinRunner editor. I know of a third party tool that is in private beta that allows you to use code snippet (als Visual Studio 2005) which will do what you are mentioning, but that is going to be an external cost. Have you looked into the paste TSL funtionality to drop in the templates?

    Thing #1 debugger: Sometimes the soft keys get screwed up. You can go in to Tools | Editor options and set them up as you desire. On this one though - what exactly is the text of the error you are seeing?
    Insanity: doing the same thing over and over again and expecting different results

  3. #3
    Senior Member
    Join Date
    Sep 1999
    Location
    San Jose,CA,USA
    Posts
    340
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    Tony .. in resp to your enquiry:
    Thing #1 debugger: Sometimes the soft keys get screwed up. You can go in to Tools | Editor options and set them up as you desire. On this one though - what exactly is the text of the error you are seeing?

    While stepping through useinmg ctr_L + F8 I would encounter Insert function. Accoring to softkeys this was F8. So I deleted it, and it appears that I am safe. (at least my intial testing says so .. never know).

    I think I will hunt down that soft key file, make a backup and delete them all. I will then come up with the actions I actually want. I must say that Winrunner has no problem getting in the users face, with thier product.

    I suppose this is good in some ways ..

    Anyway thanks Tony your input and time are valuable!
    Smoke me a kipper, I'll be back for breakfast!
    Sincerely
    Richard Weth
    Sr. QA Engineer

  4. #4
    SQA Knight
    Join Date
    Jun 2002
    Location
    Cupertino, CA, USA
    Posts
    2,164
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    [ QUOTE ]
    I think I will hunt down that soft key file

    [/ QUOTE ]

    %windir%\wrun.ini

  5. #5
    Moderator
    Join Date
    Mar 2000
    Location
    Orange County, CA
    Posts
    3,187
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    It sounds like the old :sticky ctrl state" annoyance WR has.

    If you don't release and repress the ctrl key (or alt) in between uses, it isn't recognized.

    Are you doing two ctrl-F8 clicks one after the other? If you are, try releasing the ctrl key inbetween and see how that does you.
    Insanity: doing the same thing over and over again and expecting different results

  6. #6
    Senior Member
    Join Date
    Sep 1999
    Location
    San Jose,CA,USA
    Posts
    340
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    Well I will tell you Tony and all .. I just am NOT a softkeys kind of guy! I find the entire cadre of combos a
    tad overwhelming, and Most are frankly somewhat useless.
    (these (37) I have silenced for good!)

    I did actually find out the file via filemon via sysinternals .. bpolitzer and I thankee. Also useing that
    Softkey Configuration utility was a nightmare!!!
    (that is 3 exclamation points out of a possible 5!!!!!)

    Every time I had any conflict in key settings (and how can you help not .. when there are 47 commands with key combos?!!) I got a dialog that essentially would not allow me to resolve. So instead of useing the so called convienance App == softkey.exe I simply edited the
    wrun.ini by hand .. way simpler !

    Well thats my experiance, and I certainly don't want to knock most of the features of Winrunner at large. But this particular interface was very poorly designed. Why should I cut Mercury interactive slack when I generally have my own development crew in tears by the end of a cycle!!!!
    (for the counters which is most of QA thats a poss 4/5 exclamations)
    Smoke me a kipper, I'll be back for breakfast!
    Sincerely
    Richard Weth
    Sr. QA Engineer

  7. #7
    SQA Knight
    Join Date
    Jun 2002
    Location
    Cupertino, CA, USA
    Posts
    2,164
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    They are way out of hand with the soft keys. In all my years of WinRunner experience, there's only been two I've ever found usefull:

    XR_SOFT_STOP=Ctrl_L F3
    XR_SOFT_PAUSE=Pause

  8. #8
    SQA Knight
    Join Date
    Jun 2002
    Location
    Cupertino, CA, USA
    Posts
    2,164
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    Hey, what do you think this does:

    win_type ("{label: \"!WinRunner.*\",location:0}","<kCtrl_L-kF3>");

  9. #9
    Moderator
    Join Date
    Mar 2000
    Location
    Orange County, CA
    Posts
    3,187
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    I find a couple of other softkey combinations useful, but not many.


    Ctrl_L T
    Crrl_L E
    Ctrl_L D
    Ctrl_L L
    Alt_R F5


    but other than that I think the others are just fluff to confuse
    Insanity: doing the same thing over and over again and expecting different results

  10. #10
    Senior Member
    Join Date
    Sep 1999
    Location
    San Jose,CA,USA
    Posts
    340
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winrunner edit commands and a debugger annoyance

    To answer bpolitzer

    >>> Hey, what do you think this does:
    >>>win_type ("{label: \"!WinRunner.*\",location:0}","<kCtrl_L-kF3>");

    I think if your softkeys are configured and it works, this is "A" way for for WinRunner to stop itself.


    I think there are more straightforward ways to do that:
    texit
    treturn
    AND
    I think there is some kind of pause function

    But you know .. it's all about style. Also bottom line if it works like 90+% of the time use it, and figure out a way to recover from that 10% (which is another thing Automated QA is known for).
    Smoke me a kipper, I'll be back for breakfast!
    Sincerely
    Richard Weth
    Sr. QA Engineer

 

 

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 10.71%
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 08:28 PM.

Copyright BetaSoft Inc.