The problem is build 10586 of Windows 10.
This build can prevent TestComplete from working correctly with Microsoft Edge.
(if this happens in all cases - I don't know)
I'm working SmartBear support group on my issue on Edge. Will let you guys know how it goes.
thuy:
Hi,
Just to double-check: have you verified that Edge is not allowed to run as a background process?
If the browser (Edge, Chrome, ...) is allowed to run as a background process, TestComplete finds it as a process, but, obviously, cannot find its Page object and fails to navigate to the url. (Though I am not pretty sure about the actual error thrown in this case.)
OMG - Alex, thank you! I'm not all that familiar with Windows 10 and turning OFF Edge running as a Background Process fixed my issue. My scripts are now running in Edge - albeit kinda slow! ;-) But thanks so much!
~Chris Ulisse
Hi Chris,
Great to hear that the problem is solved and thank you for the update.
> My scripts are now running in Edge - albeit kinda slow! ;-)
Unfortunately, this is a known problem with Edge. I was told by Support guys that this is caused by the 'security' patches by MS which make Edge more and more closed for the external applications and this forced TestComplete to use some other approach to drive the Edge. I was also told that SmartBear constantly works on this problem and there are chances that the performance for Edge will be improved.
Thank you, Tanya :)
