Forum Discussion

ct_biji's avatar
ct_biji
Occasional Contributor
14 years ago

Object doenot exist after multiple executions

I have an issue where the object doenot exist error pops up after couple of executions.The object does exist in the name mapping but still the error is popping up it is a recorded script to launch an application.

An error occurred while calling the "Click" method or property of the "Edit" object.

The object or one of its parent objects does not exist.


Tested Object













Alias: Aliases.pythonw.dlgTritonLogin.Edit
Mapping item: NameMapping.Sys.pythonw.dlgTritonLogin.Edit

Missing Object













Alias: Aliases.pythonw
Mapping item: NameMapping.Sys.pythonw

 Should i write a manual code to launch it is there any method to activate the login window in test complete?

Thanks,

Biji

4 Replies

  • baba_k's avatar
    baba_k
    Occasional Contributor
    Hi Biji,

    You can add your application to tested applications in test complete by doing the following:

    Right Click on your project name-> Select the option Add -> Select 'Testedapps' -> Browse the path of your application ->Click OK.

    Now write the code

    Sub test

    Testedapps.Yourapplication.run

    End sub



    The above code will open your application automatically and now try to recoed login from here..
  • ct_biji's avatar
    ct_biji
    Occasional Contributor
    Hi,

        I added my application to the testedapps still it doesnot work.its showing the same error plus some security issue.



    Thanks,

    Biji
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    The problem, as the error suggests, is that the process for your application is not found.



    While your program may be running, the NameMapping/Alias for that program may not be finding it.  This could be the case if the name mapping has a process index that no longer matches the process index in your actually application.



    Edit the namemapping parameters for your application and make sure they are set up to find your process.



    Also, make sure that you don't have more than one copy of your application running.  If more than one copy is running, that may also contribute, again, due to the mismatch in process ID.
  • Hi Biji,



    Robert is right. In your case, the tested application's process cannot be found. This can be caused by the fact that there are several processes with the same name, and the Index property of the process you actually need changes from run to run. To resolve this issue, you need to exclude the Index property from the mapping criteria for the Aliases.pythonw object and add required children to the NM scheme. See the Specifying Child Objects Required for Mapped Object Identification help topic for the information. Also, this video can be helpful for you.



    BTW, if you face an "object not found" error, the link to the corresponding help topic should be posted to the Additional Information panel of the test log. Have you tried following the suggestions provided in the help topic, the link to which has been posted to your test log? What were the results? If the help topic was not enough for you to find the cause of the problem, please let us know what problems you faced when diagnosing the problem so we can improve our documentation.