Share
ReportI'm having issues running automation tests through RSAT since the latest update of chromedriver. It seems this has included some tighter controls around private network access and this is clashing directly with how RSAT runs. As soon as a test connects to dynamics through the UI it is throwing up a message requesting a user response to either allow or block RSAT from connecting to the local network. This never previously happened, but is now effectively rendering all RSAT tests devoid as it requires someone to watch them and click "Allow" when prompted.
I've tried whitelisting my sandbox environment base url (as RSAT kicks off a unique connection each time it runs a test) but this has not impact. I can see that RSAT connects using Incognito which I think is causing an issue as it's using a temporary profile every time it runs, so it requests authorisation to access the local network every time a test runs.
Has anybody else encountered this, and how have you managed to get around it?
Categories:
I have the same question (0)
All responses (
Answers (
92
