Forum Discussion
On the slave machine, run TestExecute and then right-click on the icon in your systray. Click "Install Extensions" and check to make sure the Delphi support extension is active on that machine.
Another possiblity could be a timing problem. The object MAY be there, but calling just b.VCLObject('xxxForm') does not actually do any waiting... it may take some time for the object to be recognized. Try using the WaitVCLObject method instead and see if that improves things.
- AlexKaras6 years agoChampion Level 3
Hi,
One more possibility, considering that
for Aliases.B. [...] The process seems to only have generic windows properties.
is that the file with the debug information for the B application (B.pdb) is not deployed (copied) to the slave machine or TestExecute cannot find it there.
- tvlchkitout6 years agoNew Contributor
Thanks for the help.
Yes I put the debug info file(.tds for Delphi) with the .exe on the slave machine. I also made a debug build with debug info and TC is still not able to recognize it as a Delphi built process.
- AlexKaras6 years agoChampion Level 3
Hi,
Sounds wierd...
I would recommend to open Support case via the https://support.smartbear.com/message/?prod=TestComplete form and reference this thread.
I'll appreciate it if you update here for the benefit of others with what you will end up with Support.
- tvlchkitout6 years agoNew Contributor
Thanks for the suggestions.
I checked my TC's extenstions and clicked select all then OK. Unfortunately the problem remains.
Tried using the WaitVCLObject method with 10 seconds it still has the same problem. I can manualy click the window but TC is not able to detect it even it's there Visible.
Related Content
Recent Discussions
- 2 hours agoSubhraDas
- 21 hours agotramuntana