Forum Discussion

pravin_k99's avatar
pravin_k99
Contributor
13 years ago

DEFECT in TC 9.30 - If a child and its parent and grandparent all have extended find, then TC thows a Warning



  1. A Child has extended find


  2. Its Parent has extended find


  3. Its Grand Parent has extended find


  4. Its Great Grand Parent has extended find


  5. Try to run an action on such a child.


  6. TC will through a warning, even though it will still find the correct object for you and proceeds with the test.




"This message is posted to assist you in troubleshooting the subsequent "The object does not exist" error.


The mapped item "Login_Window", which is one of the parent objects of the missing object, has the Extended Find attribute enabled. As a result, the test engine sought for this parent object on all levels down the object hierarchy and found the following object matching the mapping criteria:



Sys.Process("javaw", 2).Window("SunAwtDialog", "Login...", 1)



If it is not the desired object, then this mismatch may be the cause of the subsequent "The object does not exist" error. If this is the case, correct the mapping criteria to identify the objects more precisely."



The same test works fine in TC 9.20 without any change.


4 Replies

  • nicktulett's avatar
    nicktulett
    Contributor
    12 years ago
    I don't think that's a defect. Extended Find is an expensive operation and may not identify the correct object., especially over several levels of hierarchy.



    If you can, find another way to identify the object, otherwise you can always trap the OnLogWarning event and reject these messages so they don't appear in the log. 
  • TanyaYatskovska's avatar
    TanyaYatskovska
    Icon for Alumni rankAlumni
    12 years ago

    Hi Pravin,


     


    According to your description, I see that the following situation might be an issue: TC posts an error to the test log saying that the object wasn't found in spite of the fact that the correct object was found, and the test execution continues successfully. Is this the case? Could you please report this behavior to our TestComplete Support team so that they could investigate it? That would be great if you sent them your entire project suite folder along with the log of the failed test execution.