Cannot read property '$$testability' of undefined
See original GitHub issueIn Protractor 5.1.1 if your Angular app has a root element other than <body>
, you’ll see the error Cannot read property '$$testability' of undefined
. This is because browser.angularAppRoot() is expected to return the current value of app root if a value isn’t passed to it, but currently returns undefined.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:42 (10 by maintainers)
Top Results From Across the Web
Protractor - Cannot read property '$$testability' of undefined
Although it's sometimes caused by documents without an html tag in the root, "Cannot read property '$$testability' of undefined" is more ...
Read more >Tag: Cannot read property '$$testability' of undefined
Tag: Cannot read property '$$testability' of undefined. Testability protractor error when your site redirects to another page.
Read more >Cannot read property '$$testability' of undefined - Bountysource
In Protractor 5.1.1 if your Angular app has a root element other than <body> , you'll see the error Cannot read property '$$testability'...
Read more >angular/protractor - Gitter
But it doesn't look like you installed global ( npm -g protractor ). ... to sync with the page: "Cannot read property '$$testability'...
Read more >unknown error: Cannot read property 'get' of undefined
WebDriverException: Message: unknown error: Cannot read property 'get' of undefined ... n } else {\n throw new Error('Cannot get testability API for unknown ......
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
Hi Contributors,
Any updates around this issue . Using protractor version 5.1.2 doesn’t resolve this issue. I have test cases suite that run one after the other and it’s quite sporadic… sometimes it works and sometimes they fail because of this issue. So, if you try to run say ~ 30 cases together , you will still get this issue using 5.1.2.
Thank you for your help.
We’re planning to do a 5.1.2 tomorrow that should include this fix.