Forum Discussion

pkunst's avatar
pkunst
Contributor
13 years ago

The Object does not exists

Hi,

the problem ist that I recorded a new Keywordtest. Since this record nothing had happend to the programm which I like to test. But allway I replay the test there are multiple error, that the object does not exists. So I used the fullnamewhich is found by the object spy. But this hastn't helped. Also I watchted whar happend during the replay of the test and theire is no the object exists at the gui.

6 Replies

  • pkunst's avatar
    pkunst
    Contributor
    13 years ago
    I already read the text because it is shown in the "Additional Info". 

    The complete text is


    "The object with the specified attributes does not exist.



    Possible causes of the error"

    I also know wich object is the problem an set a breakpoint wehre the error occures.

    I checked if the object exists, and it does. I took out the object spy at the breakpoint an looked at the name. Both, the mapped and the full name are the same.


  • pkunst's avatar
    pkunst
    Contributor
    13 years ago
    I don't know why but today was the day it sometimes worked. Not alle the time but sometimes. In the script I can see that I try to do multiple clicks on the object. It is always the same syntax, but other coordinates.

    At the beginning TestComplete can not find the object then it can be found. After this I want to click a button on a new form. Now the button is not found even if the button is there. I can see him and the object spy can find him to. I compared the names an they aret the same.



    Anoter object I TC can not find is a toolbar. If I try to click on it an error occures, butt if I record to press F10 then the first element of the toolbar is choosen. And I can go through the items with left right up and down. So this should be clear proof that the object which "dose not exists" exists.
  • rickm's avatar
    rickm
    Contributor
    13 years ago
    I'm getting errors such as "object does not exist" and "not responding" intermittantly on tests that used to run fine.



    Many of these are made to work again by overriding the default "auto-wait timeout" of 100ms to 1500ms for the particular action that is failing. I didn't bother trying to see how long is really required. I see no harm in a higher-than-required value since it continues as soon as it can.



    If the Auto-wait Timeout field is not shown in the KeywordTest editor, right-click just about anywhere in the test and select "Field Chooser".
  • dosseh_abiassi's avatar
    dosseh_abiassi
    New Contributor
    13 years ago
    Hi Patrick,



    1- After you record, it will be good to namemapped your root object by using the namemapping editor (right click on the objet line in the keyword test)

    2- Try to remove cordinates and replay



    Hope it helps