Forum Discussion

Sun-Wukong's avatar
Sun-Wukong
New Contributor
14 years ago

Exception handling broken in TestComplete 8

Hello there.


We've been using TestComplete for 2 years already and were pretty much satisfied with it's performance. But some time ago we've upgraded to a 8.7 version for testing Chome support for our web application. And that's when a problem raised.


Our product oriented on all web browsers but mainly on Internet Explorer so the main part of testing are going for IE. But IE is pretty much unstable and it usually crashing about a dozen of times during one test session, so I have a lot(a LOT) of exception handling routines in my test code to prevent tests from crashing when IE crashes.


All worked just fine with TestComplete 7.5, but became broken after upgrading to TestComplete 8.7


It seems that most of exception handling routines in TC8.7 are getting ignored and that is leading to tests getting aborted with errors like "You are trying to call the "WaitChild" method or property of an object that does
not exist" - that happens after IE crashes and of course object it was associated with isn't exists anymore, that's why there is try...catch routine around it, and test execution still breaks though this error happened INSIDE exception handling routine(inside try{} operator).


This is pretty sad since we now have all of our tests broken. I'm hoping to get some feedback on this issue. Maybe there is some new hidden setting for the TestComplete framework that I should change to make exceptions work right?

4 Replies

  • ramu6309's avatar
    ramu6309
    Occasional Contributor
    14 years ago
    Hello Denis,



    Use "IsSupported" function before you are using the property of an object.So that u won't get errors like you mentioned.



    Eg: If   IsSupported(Object,"PropertyName) Then  'Suppose if you want to get wndCaption

               Log.Message Object.PropertyName



          End if



    I hope it solves your issue



    Regards,

    Ramarao
  • sheen_mat's avatar
    sheen_mat
    14 years ago
    Hi,



    We are in the same state. We have been using TestComplete for about an year now and did  not have  issues.  I am on version 8.7. TestComplete hangs with high CPU usage. It is not able to throw exception.  Support team has been trying to help me out. But it's been in this state for more than a month now. Any help on this will be highly appreciated.





    Thanks,

    Sheena
  • Dmitry_Nikolaev's avatar
    Dmitry_Nikolaev
    Icon for Staff rankStaff
    14 years ago

    Hi Denis,



    The 'try..catch' statement can handle exceptions that occurs within the script engine. By default, exceptions that occur in a tested application cannot be handled in this way. You can find more information on this in the Exceptions That Occur in the Application Under Test section of the Handling Exceptions in Scripts help topic.



    We would like to investigate the fact that Internet Explorer crashes in your case. Please contact us directly using the Contact Support form and we will try to help you resolve this problem.