[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ui5-test-runner	^5.14.2 → ^6.0.3

---

Release Notes

ArnaudBuchholz/ui5-test-runner (ui5-test-runner)

v6.0.3

Compare Source

Bug Fixes

• navigate at DOMContentLoaded to avoid 30s nav timeout on slow UI5 loads (9966514)

v6.0.2

Compare Source

Bug Fixes

• fatal browser-launch failure exits 0 (silent CI success) (#​199) (1519194)

v6.0.1

Compare Source

Bug Fixes

• minor adjustments after release (1987884, f077d75)

v6.0.0

Compare Source

Why v6

In v5, each test page had to post its progress and results back to the runner — requiring extra server plumbing, browser-security relaxations (--unsecure), and options like --localhost. v6 flips this: the runner injects a lightweight agent into each page and pulls the state out by polling it directly. The page no longer reaches back to the runner, which removes a lot of old machinery and unlocks the improvements below.

Highlights

• Faster, more reliable at scale — a single browser instance hosts all parallel pages, with quicker page bootstrap and native caching of UI5 resources across pages.

• Driver and browser are now separate options — --driver selects the automation engine (puppeteer, playwright, webdriverio, selenium-webdriver); --browser selects the actual browser (chrome, chromium, firefox, webkit, …).

• Standard report format — reports now follow the Common Test Report Format (CTRF); junit.xml is generated by default alongside report.json and report.html.

• Live trace visualization — the dynamic HTML progress page is replaced by real-time traces via --log.

• Uncaught errors fail the page — a page that throws is no longer reported green, surfacing real defects immediately.

AI-assisted migration

A built-in MCP server exposes the live documentation — including the full migration guide — to any MCP-compatible AI client:

bashnpx ui5-test-runner@6 --mcp

Point your assistant at it and have it migrate your config option by option, working from an authoritative, up-to-date source rather than guessing. It's documentation-only (it answers questions; it doesn't run or control tests).

Breaking changes

v6 requires Node.js 24. Several options were renamed, replaced, or removed (coverage and screenshots are now off by default; --libs → --lib; browser flags reworked; --localhost, --capabilities, report generators and others removed).

See the full migration guide for an option-by-option breakdown.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 08:00 AM and 04:59 PM, only on Monday (* 8-16 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[maxreichmann]

MCP-based migration planned.
--> Disabled auto-merge till then

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.