Executing commands directly on sections?

[drptbl]

Hello, I was wondering if that's even possible.

I want to execute a command directly on some section. For example - I want to .waitForElementVisible directly on section (not on elements). Is it even possible? I've tried a lot of combinations, for example:

browser.page.topMenu().section.loginBox.section.unauthenticated.waitForElementVisible('@loginTooltip', 10000)

So it looks like this: topMenu() is my pageObject file, then there is loginBox section containing -> unauthenticated section containing -> loginTooltip section. I want to .waitForElementVisible on the last one section. How to do this? I know I can combine my sections without limitations, but how to work on them later on?

Best regards,
drptbl.

[StephenDavidson]

I use an expectation with a cb in my project. Something like:

browser.page.topMenu().section.loginBox.section.unauthenticated.expect.section('@loginTooltip').to.be.visible.before(10000);

[drptbl]

That's a good solution for assertions. Thank you!

I'm wondering - what about commands instead of assertions? Like .click? Is there any way to execute those directly on sections?

[sknopf]

Not currently but it's something we could look at adding.

A workaround would be something like:

var loginToolTipSelector = browser.page.topMenu().section.loginBox.section.unauthenticated.section.loginToolTip.selector;
browser.click(loginToolTipSelector);

You'll have to call useXpath/useCss directly if the locate strategy differs from the previous one.

[drptbl]

This works excellent for now. Thank you 👍!

Adding this feature would make less code to maintain, still it does the job and I'm happy with this :).

[Ftelf]

Hello,
About that.
var loginToolTipSelector = browser.page.topMenu().section.loginBox.section.unauthenticated.section.loginToolTip.selector;
I believe that this is not an option since you'll get only the leaf selector, not the whole construct. if the loginToolTip.selector is the same in other branch of xpath you'll get false positive. In that case the section construct does not have a sense and you can have just parent element instead.

But back to the original issue: " calling directly on section"

If I have a section which I want to use also the same way as a element, I'll add a container element into it:
elements: { container: { selector: '.', locateStrategy: 'xpath' },
Now I can use:
list.section.segmentationsContainer.expect.element('@container).to.be.present'

[drptbl]

Waiting for this PR to be merged:
#1155
should do the job.

[mrmunch]

@sknopf Do we still have to use this workaround?

[rodrigogs]

@sknopf Do we still have to use this workaround?

What would be the correct way for clicking a section element?