Forum Discussion
This isn't necessarily a problem between TestExecute and TestComplete but, potentially, an environment issue or a problem with the application under test not being compiled or referenced the same way.
I'm assuming you're testing what appears to be a Delphi project. What it seems like is, for TestExecute, some of the plugins and such referencing the objects are not turned on.
When you run TestExecute stand along, right click on the sys try and selec "Install Extensions" and make sure that all the same extensions are active in TestExecute as they are in TestComplete.
Apologies I am quite green in trying to figure out what is going on here.
Yes it is a delphi object. It does appear every extension is turned on in both applications.
- tristaanogre6 years agoEsteemed Contributor
Since TestExecute does not have an object spy, how are you getting that output of how TE is viewing the object? Is this coming through an error record in the test log? If so, could you post the whole error message including the Additional info tab?
Thanks!- Lizpuff6 years agoNew Contributor
I am using an option that was written by my husband for Test Execute/Complete to get the name as object spy does.
Here is an error I get while trying to click an item in the list box (one which T.C. can select)
- tristaanogre6 years agoEsteemed Contributor
Ok. The error probably has "Additional Information" on it. That will be helpful.
Also, could you post the code of the logic you're using to get that info?
AND... are you using NameMapping for object identification?
AND... is the OS different between TC and TE?
Related Content
- 8 years agoanmoldabra