Forum Discussion
I meant what language is the application you are testing written in. That's what determines how TestComplete identifies objects.
Sorry, the application is written in Delphi
- LinoTadros5 years agoCommunity Hero
It's a timing issue or temporary popup object creation issue.
Because it is a Delphi popup that has the confirm button that you are looking for.
Also it is very possible that the Delphi Developers pop the window using "TfrmPSBadgerOK.Create" instead of generating a persistent variable for the object, so the popup has a different temporary object name every time, so it breaks the name mapping and it is never found again.
If that is the case, you have to check the existance of the popup using the caption of the popup instead of the name of the object to get to it and click the confrm button.
Hope that makes sense
-Lino
- awhawh5 years agoContributor
I've managed to run it through TestExecute OK using command line, so it only seems to be a problem with TC
I'll speak to one of our developers to review the application's code
Thanks
- awhawh5 years agoContributor
Hi,
Initially it worked when running the test through TestExecute from command line. I decided to launch TestComplete.exe directly from the application bin directory. This also worked.
The problem was running TestComplete from the desktop icon that was created during the installation process
- awhawh5 years agoContributor
Thanks for your information
Why do you think that it's only a problem in RunAs mode? TC never has a problem finding the object in normal Run mode
- LinoTadros5 years agoCommunity Hero
I can't tell without seeing the code
I am thinking the Delphi code is checking to see if you are logged in as admin or not and firing up the popup differently in each case.
It is easy to figure out once you see the code why it is behaving that way
Cheers
Lino
- TanyaYatskovska5 years agoSmartBear Alumni (Retired)
Related Content
Recent Discussions
- 20 hours agovladd1