Could not find testability for element when use elementor or element explorer

[jalal1]

Hello,

I am trying to run elementor, in order to locate elements on my page. But i always got the same message :

ERROR: TypeError: Cannot create property 'stack' on string 'Error while waiting for Protractor to sync with the page: "Could not find testability for element."'

Same error when trying to using Element explorer.

Bug report

• Node Version: 6.2.0
• Protractor Version: 4.0.3
• Browser(s): Chrome
• Operating System and Version Windows 7
• Your protractor configuration file
• A relevant example test
• Output from running the test
• Steps to reproduce the bug
• The URL you are running your tests against (if relevant)

Feature Request

• Reasons for adopting new feature
• Is this a breaking change? (How will this affect existing functionality)

[juliemr]

I'm gonna be a stickler here - this isn't really a bug. The issue is that you're not giving element explorer enough information to tell how your angular application is set up. You can fix this by passing in a config, which has a rootElement property that is an element underneath your angular application.

But agreed that this behavior is difficult to understand - see comments in the linked issue. We're looking into simplifying.

[cnishina]

Investigated: I also agree that more information should be passed to elementExplorer. For an Angular 2 app, the useAllAngular2AppRoots flag should be set in your Protractor config. Another way to do this is in the elementExplorer console to set browser.rootEl = '';.

Elementor does not allow you to pass in a config file so for Angular 2 apps, it appears that Elementor does not support it. It appears that there is already an issue for this in Elementor. andresdominguez/elementor#47

Since this is not an issue with Protractor, I'm going to close this issue.