Forum Discussion

dbroland's avatar
dbroland
Occasional Contributor
13 years ago

Name mapping issues

I am relatively new to TestComplete and trying to get a series of tests running on a remote test box. The network suite project has been defined successfully including hosts and a series of jobs and task have been defined. Currently I have only one task enabled. When I run the task it encounters seemingly random issues with objects not being found ("The object or one of its parent objects was not found"). I can rerun the task multiple times and I will get unpredictable results. One time it may get a similar error with a completely different object and window and place in the test and I have had the test complete without errors. This is with no changes to the TestComplete project, tested application, or test platform. I'm at a complete loss as to where to start looking for problems. Any suggestions?I am running TestComplete 9.30.3373.7. The application under test is a 32 bit application running in a Windows 7 environment.

6 Replies

  • Marsha_R's avatar
    Marsha_R
    Icon for Champion Level 3 rankChampion Level 3
    Try putting a Delay right before you need the object.  We have found that the tests can run faster than objects get loaded so sometimes it is there and sometimes it is not.  The delay helps compensate for that.
  • ian_brown's avatar
    ian_brown
    Occasional Contributor
    We've just started to evaluate TestComplete and are having very similar problems on playback of recorded tests where, seemingly quite randomly, the system fails to locate objects. If a failure does occur it seems to always occur at the same point in the playback. However, on another test the same object will be recognized with no issues at all.

    It is fair to say that we've experienced very similar problems with other GUI test applications that we've tried. The problem is that unless playback is guaranteed to execute properly, then it's hard to see how the application can be of much practical use.
  • I've had the same issue when the application under test was launched twice: in the task manager, I could see 2 processes with the same name, that process being related to the object not found.



    I am completely new to TestComplete so take this answer with a grain of salt.
  • dbroland's avatar
    dbroland
    Occasional Contributor
    Continuing to attempt to track down this issue. I've watched part of an online webinar that discusses the object not found issue and I'm attempting to apply the recommended diagnosis procedure. I'm fairly convinced the object name is not being dynamically generated. However, the object is created or supplied by a third party component suuplier. Currently pursuing the theory that the object is not available at the moment that TestComplete is looking for it - i.e. possibly a lag between when the screen is displayed and the object becomes available. In the specific case I am examining, the object is a menu item. Upon running the test a second time, TestComplete found the objectand continued running w/o error. No change in TestComplete or the application.
  • dbroland's avatar
    dbroland
    Occasional Contributor
    Thanks for the input. I don't think delays for each object being accessed is feasible from a performance viewpoint given that the object not found error pops up in seemingly random parts of the application. However, I did change the Playback option "Auto-wait timeout" found on the properties tab for the project to 5 minutes (300,000 milliseconds). This seemed to help but it did not completely solve the problem. It seems like the object not found error occurs with Infragistics components (menu items and Ultrabutton). I have verified that the Infragistics Object Mapping plugin is present and enabled. We are running Infragistics 2008 vol 2 clr 2.0. Anyone have issues with these third party components?

  • Hi,


     


    Most of the playback errors can be resolved by using the steps specified in this article. Increasing the Auto-wait timeout may help, as well. However, it's not a reliable way to avoid such errors.