The application has the same name and the same path as it does on the computer where TestComplete is installed. How do I check the NameMapping properties on the computer where I am running TestExecute?
I tried bypassing NameMapping by changing the objects to their full name, but that didn't help; it couldn't find the process. Is there any way of logging the processes that are running so that I can see if it is named something different than I expect?
What properties are used to map your MyApp element?
This may seem like a "duh" question...
...but have you verified that the application is actually running on the machine when you run it from TestExecute? Can you go to the machine, either via remote or directly, run the TestExecute commandline and verify that it is launching your application?
Also, something to just make sure of that the application is running under the same user as the TestExecute process... it's possible that this could "hide" your application from TestExecute as well, depending upon privilege levels.
I really don't know what properties are used to map the application. I have TestComplete open, and I'm looking at Mapped Objects, but I don't know what to look for.
The application is running, I can see it. I start the application manually before running the test, because there is manual setup I have to do anyway. I may add functionality to have my script start the app later. I could try having the script start the application and see if that helps.
As far as I can tell, the application is running under the same user as TestExecute is.
OK... under Mapped Objects, you should see a collopsed node that says "Sys". Expand that. Somewhere in that list is your app (you called it "MyApp"). Click on that.
In the right hand side then, you should see all the properties being used to map your application. For example, in this screenshot, I'm mapping the Windows Paint application as Aliases.mspaint and it is using the simple criteria that it has a process name of "mspaint".
If, on the off chance, MS Paint starts and it has a DIFFERENT process name than "mspaint", even though the application is running, Aliases.mspaint will return an object not found error.
