This is not yet expected to work - custom locators aren't yet supported for angular 2.

@jquerygeek - current workaround for me is to use CSS locator:

// let dashboardItems = element.all(by.repeater('exchange in exchanges'));
let dashboardItems = element.all(by.css('bx-dashboard-item'));
expect(dashboardItems.count()).toBe(8);

Hello,

When are you willing to implement these features ?
Unfortunately, Protactor is losing its charm when we get elements with "by.css" ...

Thanks,

This is still on the list - we're working with Angular to design the best way to create these angular specific locators going forward. It's difficult because the angular compiler does not export all the information we need (for important performance reasons), so this needs to be done carefully.

The recommendation continues to be using by.css, which I find to be versatile and concise in most situations :)

Thanks for your reply Julie !

+1 for by.model and by.repeater - makes for less brittle and more data-driven tests. Happy to help review stuff/doc stuff/test stuff...

Try this:
var data = element.all(by.css('table[name='' + TableName + '']')).all(by.css('tr td'));
expect(data.get(0).getText()).toEqual('0');

Any further updates regarding use of by.repeater() with Angular2 repeater *ngFor, or still we need to follow by.css?

@nithinkrishnan I think we need to continue using the .css as they do not have anything yet to support for ngFor like they have for repeater.

Any clue when this issue will be closed ?

^

@DMadrid What do u means :) :) ?

bump

Guys, any updates?

With just 2 small releases since February, Protractor doesn't seem to be getting the attention that angular is getting.

As a reason even I do not prefer using protractor anymore.

Is Protractor just dead now? Without the Angular integration, it's just Web Driver and might as well use Selenium at that point. With all the headaches that comes with. :-(

Is this planned to be fixed in any upcoming release?

by.css is powerful but brittle. by.model and friends are superior in many cases -- is there any intent to implement this someday, or has the protractor team decided to drop support for these features for Angular 2+? Since this issue has been sitting untouched for 12 months, it would be nice to hear the team's current thoughts.

It seems to me that protractor gives us a lot in the waiting/timing area that we would have to sleep() us through without.

As long as I have control over the source code for the stuff I'm testing, I can always insert id's, names or css classes to hopefully uniquely identify fields.

But support for binding and model would sure be appreciated.

Is protractor good only for angular 1? I'm kinda not sure, there's no good documentation about how to use it effectively for angular 2+