SPONSORS:






User Tag List

Results 1 to 3 of 3
  1. #1
    Senior Member
    Join Date
    Jan 2001
    Posts
    750
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Running consecutive test plans, pro/cons. Cause Internal Error.

    I run many test plans one after another in a loop from Perl using command lines.

    There is one case(might be more) where it can't start the following test plan, because of an "iternal error AppID"..not found or responding(forgot which one). After the failure I see 2 browsers. One which obviously is from the previous test plan and the other is at the beginning of the script of the second test plan.

    Any idea solution, idea, comments, or suggestions?



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

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

    Re: Running consecutive test plans, pro/cons. Cause Internal Error.

    I've seen this happen with Netscrape before when the memory leaks in Navigator become too much and the browser just hangs. SilkTest can't get the existing one to work, so it tries to launch a new one, which it does successfully. However, then it tries to close the old one, which is still not responding, so...DOA.

    Might want to modify/write a TestPlanExit that kills the browser. Or, what I did once, was keep a counter in an external file and after every twenty or thirty testcases kill the browser. The next testcase will restart it.

    - Dave


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

  3. #3
    Member
    Join Date
    Jan 2001
    Location
    Westborough, mA, USa
    Posts
    91
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Running consecutive test plans, pro/cons. Cause Internal Error.

    I had the same problem and i did get around it by killing the browser, and restarting it after each testcase using a TestCaseExit() function.

    Hope this helps



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

 

 

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 12:43 AM.

Copyright BetaSoft Inc.