Forum Discussion

javance's avatar
javance
Occasional Contributor
10 years ago

TestComplete 10.6, 10.5 continuously crash

As in, the TestComplete window closes and the process terminates without cleanup.

 

It happens when looking for a particularly deep element in a page on IE 11, using native web finder methods and xpath methods.  It happens after navigating to a new page in IE 11.  It happens when the browser is there, but for some reason can't see it.  Instead of gracefully providing an error message and continuing, poof.

 

Sometimes instead of blowing up, it can't find an element on the page.  I look for the element in F12 and wow, there it is.  Run the script again, and sometimes it finds the exact same element on the exact same line of script.  Sometimes not.  Sometimes, instead of just not finding an element, all active content on the page dies.  Sometimes the entire page being tested against freezes and the browser must be closed.  This behavior is not observed when testing the application manually.

 

Environment:  Windows 7 with all updates.  IE 11 with all updates.  TestComplete 10.5, 10.6.

 

Offending pages are OUO, sorry.  However, Telerik Controls are extensively used.

 

 

  • jorgesimoes1983's avatar
    jorgesimoes1983
    Regular Contributor
    10 years ago

    Today I started experiencing the same issue.

     

    TestComplete just closes without notice...

     

    Multiple experiences of the issue while executing this code (partial code):

     

    obj = objIFrameContent.FindAllChildren(new Array("objectIdentifier", "ObjectType"), new Array("statusimg_0", "Image"), 20);
    obj = (new VBArray(obj)).toArray();
    obj = obj.reverse(); 
    if (obj.length > 0)
    Log.Message(obj.length);
    }

    • javance's avatar
      javance
      Occasional Contributor
      10 years ago

      Removing security updates is a complete non-starter.  Corporate IT would not take kindly to that and probably would push out the change again on the next forced update.

       

      Switching to Firefox 36 resolved all the crashing problems.  However working with Firefox has its own problems.  Sometimes I will get "there was an attempt to perform an action on a zero-sized window" error.  Under firebug the element has size and visibility.  The element is there, visible on the screen.  I can manually click on the element.  But the TestComplete object I retrieved to fire the Click() method on shows Height and Width at zero.  The exact same element does not show as zero sized when using IE 11.

  • javance's avatar
    javance
    Occasional Contributor
    10 years ago

    Aaaand now TestComplete won't work with Firefox.  "This Firefox Version Is Not Supported".  This is from going from 36.02 to 36.03.

     

    It's like TestComplete wants me to find a competing product and use that instead.