-
Notifications
You must be signed in to change notification settings - Fork 2.3k
protractor can't find nested elements when using by.repeater and ng-repeat-start #2365
Comments
Gotta love being lectured at :) In your repo, is there any particular way you want me to start up the server for the app? Or should I just hop into |
Sorry I was a little frustrated that it wasn't re-opened or did you not see my message in the other issue? I was just using http-server - you could use httpster if you like too. and just open a browser at http://localhost:8081/app/#/view1 that's the output. Run the protractor tests as normal. |
Preliminary finding: our locators totally fail for |
Thanks for the update! |
This bug was introduced when by.exactRepeater was Discovered while investigating issue angular#2365
Ok, so, this is actually expected behavior (see the last example in http://angular.github.io/protractor/#/api?view=ProtractorBy.prototype.repeater). You should probably use a |
This bug was introduced when by.exactRepeater was Discovered while investigating issue angular#2365
When you use ng-repeat-start with nested objects protractor isn't exhibiting the expected behaviour.
I have create a test application to simulate this scenario with the following code:
Controller:
View:
Protractor Test:
I would expect that it would only return the 2 test objects not those plus the other nested ng-repeat objects.
Here is a full repo with all the code and tests: https://github.com/jjulicher/NestedRepeaterTest
@sjelin Please don't close this if you don't understand nested repeat elements.
As per the docs:
Special repeat start and end points
To repeat a series of elements instead of just one parent element, ngRepeat (as well as other ng directives) supports extending the range of the repeater by defining explicit start and end points by using ng-repeat-start and ng-repeat-end respectively. The ng-repeat-start directive works the same as ng-repeat, but will repeat all the HTML code (including the tag it's defined on) up to and including the ending HTML tag where ng-repeat-end is placed.
The text was updated successfully, but these errors were encountered: