Skip to content

by.options locator is used incorrectly #6

@szmeti

Description

@szmeti

We have an NgOptionsLocatorStrategy that matches on ng-options. At the moment we use this to generate a selector for the select, but Protractor returns the nested options if by.options is used. Because of this all of the generated methods are incorrect (our methods assume they work with the select tag).

For now, I have removed this locator strategy from the config. We need to test the generated methods with a Protractor test and adjust if necessary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions