SPONSORS:






User Tag List

Results 1 to 7 of 7
  1. #1
    Senior Member
    Join Date
    Jul 2001
    Location
    Elizabeth, CO, USA
    Posts
    653
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    WaitForReady in 6.0!

    Folks.
    Warning: seems that Browser.WaitForReady's optional argument now defaults to 0 rather than whatever you have set in Options/App Ready Timeout.

    So, if you're using Browser.WaitFoready () without an argument, you'll get a lot of Application Not Ready errors when it times out IMMEDIATELY.

    Well, okay: A colleague here just pointed out you'll only get one such exception. Per testcase.

    So, you'll need to (a) complain to Segue, and (b) change your current Browser.WaitForReady() calls to:
    Handy.

    - Dave


    ------------------
    Amelior Technology
    dreed@ameliortech.com

    [This message has been edited by dcreed (edited 11-14-2002).]
    WaltzingRhino.com
    A concerned Borland customer, a fly in the ointment, a wrench in the works.

  2. #2
    Member
    Join Date
    Aug 2002
    Location
    Raleigh
    Posts
    31
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: WaitForReady in 6.0!

    I had just run into that when you posted it. Thanks alot for the heads up. I'll try injecting that line of code into my cases to see if that works.

    ------------------

  3. #3
    gcs
    gcs is offline
    Junior Member
    Join Date
    Jun 2001
    Location
    Cambridge MA, USA
    Posts
    12
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: WaitForReady in 6.0!

    Hi,
    It's been opened as a defect in Segue's system. You beat me to posting it here...

    I'm also seeing some windows that were previously seen as browser windows that are now Dialog Boxes...

    Yuk....
    George

    ------------------

  4. #4
    Senior Member
    Join Date
    Jul 2001
    Location
    Elizabeth, CO, USA
    Posts
    653
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: WaitForReady in 6.0!

    I've got case 68019 if anyone is interested.

    ------------------
    Amelior Technology
    dreed@ameliortech.com
    WaltzingRhino.com
    A concerned Borland customer, a fly in the ointment, a wrench in the works.

  5. #5
    Senior Member
    Join Date
    Dec 2001
    Location
    Bozeman, MT, USA
    Posts
    265
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: WaitForReady in 6.0!

    wouldnt it be more beneficial to change it in the WaitForReady method itself than change all of your calls? I would open the WaitForReady method and find where the wait time is getting defaulted and set it to Agent.GetOption (OPT_APPREADY_TIMEOUT)

    Granted this would require copying in a new browser.inc into all of your silk machines but most of you are probly already installing custom defaults.inc and other files in the silk dir.

    ------------------
    Ryan McCullough
    Accelrys Inc.
    ryan@accelrys.com

    [This message has been edited by rmccullough (edited 11-14-2002).]
    Ryan McCullough
    RightNow Tech. Inc.

  6. #6
    Member
    Join Date
    Sep 2002
    Location
    Chicago, Illinois, USA
    Posts
    90
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: WaitForReady in 6.0!

    Is any way to override the function Browser.WaitForReady () to Browser.WaitForReady(180)? or to override any function in Browser declaration?

  7. #7
    Senior Member
    Join Date
    Jul 2001
    Location
    Elizabeth, CO, USA
    Posts
    653
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: WaitForReady in 6.0!

    Sure...you could modify browser.inc, but I wouldn't recommend it. I've had problems modifying core SilkTest include files and subsequent attempts to patch or upgrade SilkTest failing because it won't update that file that the user messed with, meaning that you're left with an old file when the new file may have some more important fixes in it.

    This problem was fixed in SilkTest 6.0.1. Essentially, the default value passed to Browser.WaitForReady now uses the OPT_APPREADY_TIMEOUT value that you set in the Agent Options DialogBox. Like it always was supposed to do.

    - Dave
    WaltzingRhino.com
    A concerned Borland customer, a fly in the ointment, a wrench in the works.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin 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 07:27 PM.

Copyright BetaSoft Inc.