We are working on Desktop Application.
TestComplete and Application are installed in Remote machine.
Connecting to Remote machine via VPN and
executing the scripts in TestComplete which is installed in Remote machine.
But the scripts are not executing and generating errors like "Waiting for objects",
i.e controls are not getting identified of the application to be tested.
TestComplete Version: 14.60.274.7 x64
Any suggestion would be greatly appreciated.
> Any suggestion would be greatly appreciated.
Login to the remote machine, start TestComplete and verify if tests can be executed with or without errors.
Debug errors if any.
Yes, we are executing the scripts in Remote machine in TestComplete after login to the remote machine.
Scripts are executing perfectly in our local machine but in Remote machine with the same steps, it is not identifying the various objects of the application.
With TestComplete installed on the remote machine you have all power of its IDE and debugger. So just open test project on the remote machine and check with the Object Browser how controls are identified there. Debug and figure out the differences between local and remote machines which cause test code to fail.
Thank you for swift reply.
Yes Alex, there is a proper object mapping to the controls in remote machine, same mapped objects are using in
scripts. Scripts wise there is no difference between local and remote machine. Generating the error in the log as "The object "XXXXXX" does not exist. But the object will be available in name mapping window and mapping to the control can see from the Object Browser.
I believe this may not be the problem with object mapping because all the scripts are generating the error like
"Waiting for the object".
Executed TestComplete and Application in an Admin mode but still problem exists.
Any other thoughts?
I wonder if your Name Mapping used from the working side is throwing off the Remote side when being run.
I do not use Name Mapping.
I do scripting and not KeyWord scripts.
I would suggest on the Remote machine ... try to create/record a new script there and run it.
From the broken side, maybe in your test script add Log.Message statements along your script flow to see
where the script run is executing to at all. If the script run is proceeding into your script something is running.
Again, you may need to look specially into your Name Mapping to be sure your Remote machine has no issues on how those are setup vs. your local side.
Generally Test execution requires screen to be active, on disconnecting the remote desktop it does not find any object and test will fail stating Waiting for objects.
Use batch file or the below command to get disconnected from the remote desktop and keeping the Machine active.
Batch file code to execute in Remote Desktop :
for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (
%windir%\System32\tscon.exe %%s /dest:console
@ParimalaDoddi Looks like you've received a couple more suggestions, do they answer your question? If so, please mark the best one as a solution.