You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did quite some debugging and it turns out there is a difference in our project's wdio test configuration.
We are not using 'chromedriver' in service list. So the wdio defaults to puppeteer in our case. That is not dealing well with caching the retrieved elements and fails the test with 'notFound' timeout when we try to access control method.
This discussion was converted from issue #287 on June 21, 2022 15:47.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I did quite some debugging and it turns out there is a difference in our project's wdio test configuration.
We are not using 'chromedriver' in service list. So the wdio defaults to puppeteer in our case. That is not dealing well with caching the retrieved elements and fails the test with 'notFound' timeout when we try to access control method.
Please try using this configuration:
And run this test on your Sample page:
You will get a timeout on
await button.getText()
So if you are supporting the configuration without chromedriver or standalone-selenium services, then this bug should be looked into.
Originally posted by @edvardas-kireilis in #267 (comment)
Beta Was this translation helpful? Give feedback.
All reactions