Timeout with angular 4/2 app with protractor 5.x
See original GitHub issueProtractor 5 timeout with angular 4/1 hybrid app’ It seems to timeout with waitForAngular method. I turned off waitForAngular and protractor 5 will go to next command. I try a few things and none to work:
- Downgrade to angular
- add or remove useAllAngular2AppRoots: true in the config.
- Try prortactor 4.x
Bug report
- Node Version:
6.10.4
- Protractor Version:
5.1.1
- Angular Version:
4.0.2
- Browser(s):
chrome
- Operating System and Version
Mac Sierra
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:13 (3 by maintainers)
Top Results From Across the Web
Protractor Locator Time Out exception for AngularJs application
I setup a sample project based on the items you've posted and this test appears to be working for me.I'm not sure why...
Read more >angular/protractor - Gitter
1) Protractor Demo App should have a title Message: Error: Timeout - Async callback was not invoked within timeout specified by jasmine.
Read more >Angular 2 & Protractor Timeout: Here's How to Fix It
If testing your Angular 2 application with Protractor fails with a timeout, your asynchronous operations might run in the wrong zone.
Read more >Protractor Testing Tool for End-to-end Testing of AngularJS ...
Protractor testing tutorial - it's an end to end behavior driven ... sendKeys(5); element(by.model('operator')).click(); element(by.xpath(".
Read more >CHANGELOG.md
Modern angular apps now default to using all app hooks, and ng1 apps now check ... 4.2.x required by selenium-webdriver (#3534) # 4.0.5...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@NickTomlin We’ve been seeing this issue as well with a hybrid angular 4 app. A good simple base case for this would be codecraftpro/angularjs-migration-workshop repo.
The step-7 branch is where you can see the issue. I just put together a simple protractor 5.1.1 test that navigates to the site and tries to gets the page title and it times out.
I have a hybrid Angular application (6.1.4 and 1.6.9) that needs to use Angular Material in AngularJS components. Angular Material (1.1.7) seems to render animations all the time periodically inside angular zone causing protractor E2E tests to time out. Does anyone have any idea how to force all third party components to poll outside Angular zone so that protractor E2E tests can be run for the application without timing out?