-
Notifications
You must be signed in to change notification settings - Fork 2.3k
both angularJS testability and angular testability are undefined #5177
Comments
@jagdheesh-github my friend, it is not just the move to Windows 10 nor is it your code. What versions of protractor and webdriver-manager are you running on the 2016 VM? Cheers, RW It seems that the combination below has introduced significant instability in the execution of Protractor. --protractor v6.9.0 I now also have the cryptic catch-all: "Error while waiting for Protractor to sync with the page: "both angularJS testability and angular testability are undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details"
This is a common and well-documented error, but not one that I have encountered with previously what was a rather robust Protractor. I've tried several dozens of solutions for this regarding timeouts and timing, (No timing changes work and none were needed previously to get my tests to run.) but I believe that the timing is a red herring and some change made from previous versions causes even the simplest examples not to work, P.S. I used the simple example from https://www.protractortest.org/#/tutorial C:\Users\Roaky\Protractor\node_modules\protractor\node_modules\jasmine-core\lib\jasmine-core\jasmine.js:3190 Cheers |
I haven't run into this error yet but I'll try it out when I get back from vacation. If this is a bug you want fix, please also feel free to contribute. |
This comment has been minimized.
This comment has been minimized.
@RoakyWood protractor : 5.4.2 |
I am facing the same Issue with Mac OS X as well. I am getting the same above errors : C
I am using below versions : |
I also experienced this following the https://www.protractortest.org/ setup and example. node v10.15.3
|
My protractor scripts were running fine on Windows 10 Pro. but when i launch them on Windows server 2016, then they throw the below error.
E/launcher - Error: Error from waitForAngular: both angularJS testability and angular testability are undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details.
When i launched the same scripts on another windows 10 pro VM, initially i saw above error , later i fixed it by including a simple command "browser.waitForAngularEnabled(false);" inside the OnPrepare() function of protractor config file. The same trick is not working if i run the scripts on windows server 2016 VM.
Any reason why this error occurs frequently and any resolution for this ?
The text was updated successfully, but these errors were encountered: