chore(test): migrate wdio off legacy 'devtools' service to WebDriver/BiDi - #234
Merged
Merged
Conversation
…BiDi WebdriverIO v9 drives Chrome over the standard WebDriver protocol (with BiDi negotiated automatically), so the puppeteer-based 'devtools' automation service is obsolete. Remove it from wdio.conf.js services and drop the devtools + @wdio/devtools-service devDependencies. This removes the puppeteer-core / tar-fs / extract-zip / adm-zip / ws dependency chain that carried the bulk of the dev-only high advisories (226 packages removed; advisory count 38 -> 30). wdio.conf.js loads cleanly (services: ['ui5']); unit/CI suite green (566 passing). UI test suite (needs Chrome + live server on :3010) to be validated before merge.
# Conflicts: # npm-shrinkwrap.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #233. Clears the bulk of the remaining dev-only high advisories by retiring the legacy WebdriverIO
devtools(puppeteer-based) automation chain.Changes
wdio.conf.js: remove'devtools'fromservices. WebdriverIO v9 drives Chrome over the standard WebDriver protocol with WebDriver BiDi negotiated automatically, so the puppeteer-based automation service is obsolete.package.json: dropdevtoolsand@wdio/devtools-servicedevDependencies.This removes the
puppeteer-core/tar-fs/extract-zip/adm-zip/wschain — 226 packages removed, advisory count 38 → 30 (high 27 → 20).Verification
wdio.conf.jsloads cleanly — resolvedservices: ['ui5'],devtoolsgone.npm run test:ui, needs Chrome + a live server on:3010) not runnable in this environment — please validate before merge.Remaining advisories (all dev-only, out of scope)
webdriver/webdriverio/@wdio/*,deepmerge-ts, residual@puppeteer/browsers/extract-zippulled for driver management). npm's suggested "fixes" are downgrades to wdio v7/v8 — wdio v9 is already latest; real fix is upstream.chromedriver@^150→adm-zip— clears with a routinechromedriver@^152bump (tracks the Chrome major); deferred so it can be validated with the UI suite.vite/esbuild— viavitepress(docs build); major bumps, separate.sap-hdb-promisfiednestedbrace-expansion/js-yaml,exceljs→uuid— upstream / not reachable (see chore(deps): patch dependency vulnerabilities (audit fix + qs/brace-expansion overrides) #233).