SPONSORS:






User Tag List

Results 1 to 8 of 8
  1. #1
    Senior Member
    Join Date
    Oct 1999
    Location
    Tyngsborough, MA
    Posts
    211
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Fault trapping not working.


    Silk refuses to trap a crash in my AUT's uninstall program. I have the fault trapping turned on for the GUI and the agent.

    Is there anything else to turn on?

    Is this feature very reliable?

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

  2. #2
    Senior Member
    Join Date
    Jan 2001
    Posts
    750
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fault trapping not working.

    What kind of fault tracking are you using?

    I usually use do..except, and it works.
    There is one instance of Exists() condition where if my windows add duplicate reference silk will call for an exception(obviously a bug). Exists() should never return an exception. Then in the except clause add print(ExceptCalls(),ExceptData()).



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

  3. #3
    Senior Member
    Join Date
    Oct 1999
    Location
    Tyngsborough, MA
    Posts
    211
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fault trapping not working.

    different topic.

    in the extensions enabler you can turn on fault trapping for specific dll's and exe's. you have to turn it on in the extension enabler for the gui and the enabler for the agent.

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

  4. #4
    Senior Member
    Join Date
    Jun 2000
    Location
    Sunyyvale CA USA
    Posts
    422
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fault trapping not working.

    If your DLL is not raising any exception that Silk can catch, it does not work. Test yr DLL and then execute yr Silk script.

    ------------------
    Sree
    Sree

  5. #5
    Senior Member
    Join Date
    Jan 2001
    Posts
    750
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fault trapping not working.

    Still it doesn't matter what you do, do..except will catch the problem. It might raise exception at different script steps but it will be caused by your crash. Do you understand?

    If your uninstall crash, and the next step is to click on something then an exception will raise.

    quote from help "You can have SilkTest trap system errors (general protection faults)"
    Are you just relying on fault trapping system for error handling? You better have something else in place.

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

  6. #6
    KS
    KS is offline
    Senior Member
    Join Date
    May 2001
    Posts
    265
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fault trapping not working.

    To use do..except you have to know where to place it. With fault traping it is not an issue. besides after crash only thing you'd usually want is to move to the next testcases that 's what fault trap does.
    If your fault trap is not trapping exception it may not be pointing to the correct .dll or .exe which is causing it.

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

  7. #7
    Senior Member
    Join Date
    Apr 2001
    Location
    San Diego,CA,USA
    Posts
    108
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fault trapping not working.

    fault trapping is totally un reliable I have had bad experience with it so I don't go there any more and I agree with godknows you should handle everything within your scripts.

    I handle such situations in testcase exit when ever and exception occurs it gets passed over to testcaseexit function as a boolean at that point you capture the screen recover to base state and go forward to the next test. If the crash has occured then just kill the app and proceed.

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

  8. #8
    Senior Member
    Join Date
    Jul 1999
    Location
    Bellingham, WA USA
    Posts
    1,323
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Fault trapping not working.

    I tend to agree. I never use fault trapping because I've found it more of a problem than a help.

    KS, I have a template our team uses which places everything for each TestObject in a do/except. This way, anything that goes wrong with a particular test scenario will be caught by the except. If the individual code writers want to place other do/except routines within the do of the outer layer, that's fine, but the outer layer will still catch any exception that is thrown.

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

 

 

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 09:20 AM.

Copyright BetaSoft Inc.