Skip to content

wdi5 v3 // ancestor selector broken? #713

@johannesrue

Description

@johannesrue

Hi there!

Since upgrading to v3 i'm facing an issue where an selector using the ancestor property is failing when using browser.allControls.

The application which is tested is the same as before upgrading to v3, same UI5 version. App code hasn't been changed.

The selector looks like this:

controlType: "sap.m.Button",
viewName: sViewName,
i18NText: {
    propertyName: "tooltip",
    key: "DELETE"
},
ancestor: controlType: "test.commons.Card",
  viewName: sViewName,
  properties: {
      headerTitle: sTitle
  }

I have tested various combinations:

Using browser.allControls without the ancestor property ✅
Using browser.allControls with the ancestor property ❌
Using browser.asControl with the ancestor property ✅

The card is not a direct parent of the button, but this shouldn't be a problem, at least when using browser.asControl.

Is this reproducable for you?

Thank you so much for your great job maintaining wdi5 👍

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions