v1.5.0 introducing $control.exec(), script timeout alignment, an async "waitFor" queue and more #467
vobu
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
v1.5.0
is out, containing 3 features and some important dev-time changes.$control.exec()
@philippthiele contributed the
exec()
method. It allows coding logic in Node.js-scope to run in the browser-scope 🤯This makes complex browser-side operations on a control in
wdi5
tests possible w/o piling up time penalties of constant roundtrips between the Node- and browser-scope!Think of it as your hyperspace shortcut to reach through to the browser when coding
wdi5
😆More in the 📝 → https://ui5-community.github.io/wdi5/#/usage?id=exec
script timeout alignment
When configuring a custom UI5 timeout (https://ui5-community.github.io/wdi5/#/configuration?id=waitforui5timeout), the corresponding setting is automatically applied to all browser script timeouts in WebdriverIO in general (https://webdriver.io/docs/timeouts/#session-script-timeout)
No need to manually align these settings anymore in tests!
async
waitFor
queueAnother excellent contribution by @philippthiele: under the hood,
wdi5
now maintains an asyncwaitFor
queue for doing Node-browser-roundtrips.This will hopefully prevent the random appearances of "waitAsync is already running" errors 🐛🔫
Node
16
is the new defaultWith Node
14
having reached "end of life" (2023-04-30, https://nodejs.dev/en/about/releases/), we dropped it officially fromwdi5
, defaulting to Node16
.first step towards testing at scale
We moved all Authentication (https://ui5-community.github.io/wdi5/#/authentication)-related tests to BrowserStack to assert the functionality across OS and browsers.
Next step: run the entire 200+ tests regularly across all major desktop- and mobile-OS and -browser 📈 !
Beta Was this translation helpful? Give feedback.
All reactions