Forum Discussion

sgoulet's avatar
sgoulet
Contributor
2 years ago

objects previously recognized on desktop app

When beginning this project, I went through the exercise of getting objects to be recognized by test complete. I have a number of objects whose class is reported as WindowsForms10.Window.8.app.0.1986...
Desktop Testing
Object Recognition
  • sgoulet's avatar
    sgoulet
    2 years ago

    I have found the issue. At one point, I changed the user logged in to the application under test (AUT). To do so, I needed to run TestComplete as administrator. When I performed the upgrade, the shortcut which I had set to run as administrator was overwritten. I had no knowledge that object recognition required this as I had changed it for a different reason. I also had no visual indication that the shortcut was changed. Admittedly I did not notice the absence of the dialog box I was accustomed to seeing when opening TestComplete for administrator priveledges. When I updated the shortcut to tun TC as administrator, the recognition appears to have resumed.

sgoulet's avatar
sgoulet
Contributor

In theory, our AUT does not require elevated permissions. Because I am opening the AUT under a different user, which uses windows auth, I needed this. Which ... I honestly do not know why. 

 

When I test manually, I do not open my AUT with elevated permissions.

AlexKaras's avatar
AlexKaras
Champion Level 3
2 years ago

> I am opening the AUT under a different user

This might explain things.

It is my guess, that initially, when you were creating NameMapping, you started application using your credentials. If my guess is correct, then TestComplete was executed in the same context (yours) and did not require elevated privileges to access application's internals.

When application was started using different user credentials (i.e. it was started like 'Run As...', not by just logging-in as some user), then TestComplete and application appeared to be in different contexts and thus TestComplete required elevated privileges to get access to the application's context.

https://support.smartbear.com/testcomplete/docs/testing-with/tested-apps/desktop/run-modes/run-as/index.html and related articles might provide additional information.