You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our TeamCity agent (buildtest2) can run our WinAppDriver tests only when the agent user (builder) is logged in via remote desktop. If not, then the WinAppDriver can find the element, but not click on it. Log snip from the TeamCity build log below.
Windows is set to Developer mode, and the tests run fine if I am remoted in as the same user as TC uses to run them, I can see the app open and stuff is clicked not problem, the tests pass that way.
Any ideas how to fix? Is running in TeamCity headless mode not supported? The TC build agent is run as a process, not a service, so I can see that as a cmd window when I remote in, this was due to requirements from other tests. Not sure if that matters.
Currently, our TeamCity agent (buildtest2) can run our WinAppDriver tests only when the agent user (builder) is logged in via remote desktop. If not, then the WinAppDriver can find the element, but not click on it. Log snip from the TeamCity build log below.
Windows is set to Developer mode, and the tests run fine if I am remoted in as the same user as TC uses to run them, I can see the app open and stuff is clicked not problem, the tests pass that way.
Any ideas how to fix? Is running in TeamCity headless mode not supported? The TC build agent is run as a process, not a service, so I can see that as a cmd window when I remote in, this was due to requirements from other tests. Not sure if that matters.
The text was updated successfully, but these errors were encountered: