Replies: 2 comments 7 replies
-
|
@joshden we have changed the |
Beta Was this translation helpful? Give feedback.
-
|
Hi @christian-bromann , Thank you for the reply. As for validating the displayedness of an Furthermore, it can simplify the code to simply check the displayedness of an And I see your point about arguing this is actually a fix rather than a regression as it may not really semantically make sense to check if an |
Beta Was this translation helpful? Give feedback.
-
WebdriverIO for a while now automatically waits until elements become available before interacting with them.
You should use either of |
Beta Was this translation helpful? Give feedback.
-
No, the error only happens when I was waiting for the Regarding the describe("select and option elements", () => {
it("selects the option", async () => {
await browser.execute(() => {
const select = document.createElement('select')
select.innerHTML = '<option>Option 1</option>'
document.body.insertAdjacentElement('beforeend', select)
setTimeout(() => select.innerHTML += '<option>Option 2</option>', 5000)
})
const $select = $('select')
await $select.selectByVisibleText('Option 2') // WDIO 9: Error: Option with text "Option 2" not found.
})
})Interestingly, this does correctly wait for the option to be present: await $('//select/option[.="Option 2"]').click()So maybe in this case, what would you think about enhancing the BTW, Thank you for all your work on WDIO over the years. I really appreciate it. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @joshden , I've raised a PR to ensure we wait for the option to become available when using these select methods, see #14213 |
Beta Was this translation helpful? Give feedback.
-
|
Great, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I see another case where I was waiting for await browser.execute(() => {
const select = document.createElement('select')
select.style.display = 'none'
select.innerHTML = `
<option value="1">Opt 1</option>
<option value="2" selected>2 option</option>`
document.body.appendChild(select)
setTimeout(() => select.style.display = '', 2000)
})
const $option = $('select > option:checked')
await $option.waitForDisplayed()
console.log({ text: await $option.getText() })But the In WDIO 9, here is what I am using: const $select = $('select')
const $option = $select.$('option:checked')
await $option.waitForExist()
await $select.waitForDisplayed()
console.log({ text: await $option.getText() })Is there something simpler for this? Thanks. |
Beta Was this translation helpful? Give feedback.
-
I would not use |
Beta Was this translation helpful? Give feedback.
-
Yes, that's what I ended up doing. It's just that in WDIO 7 I could simply wait for the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We are in the process of converting a large code base from WDIO 7 to WDIO 9. In cases where a
<select>element is displayed, in WDIO 7.16.4, the child<option>elements were also reported as displayed. However, this behavior appears to have changed sometime between this and 9.9.1. In 9, it is reporting isDisplayed of false. This is the case both before and after clicking the<select>element.Here's a simple test demonstrating this:
WDIO 7 yields this output:
But we see this output in WDIO 9:
Is this an expected change in behavior? I didn't find much regarding this with a quick google search. If this is expected, perhaps it should be documented as a breaking change (if it isn't already)? Thank you.
Beta Was this translation helpful? Give feedback.
All reactions