Open alex1yaremchuk opened 4 years ago
Help myself https://github.com/Microsoft/WinAppDriver/issues/477
It seems to be as designed.
Open question - how to set up CI, nightly builds with this limitation?
Issue can be closed I think.
What service are you using for CI? On Azure DevOps it is recommended to use an interactive agent for UI automation scenarios. DevOps should automatically take care of the logging in process for the agent.
You'd want to make sure whatever CI service you have is able to bypass the lock screen.
Hi, thanks for the reply!
We're using TFS Builds. Server version is 2019.0.1
Our admins say that any auto-login is unsafe. Is there some resource about security of using interactive agents (whatever it is)?
Windows automation scripts need to interact with the desktop, an active session is a prerequisite since the dawn of times. You will need an active, unlocked machine. There's no way around it.
Hi, Help needed!
I used session.Mouse.MouseMove for my simple WinForms test to move mouse to the control which I wasn't able to locate with ids (inspect displays it outside of the application's tree, might be a separate question why).
It worked fine as I was running it, but on night run it failed as
Might be it has something to do with the locked state of the PC?
Thanks!