Person

Arnaud Buchholz

Capabilities1

Provides 1
UI5 testingUI5UI5 testingcapabilityProving a UI still works — unit tests over controllers and formatters, integration tests that drive real controls, and end-to-end runs against a served app.

Entries2

Group by
EntrySignals
Maintains1
ui5-test-runnerv6.0.1
none

Command line running UI5 QUnit and OPA tests in parallel

Contributes to1
wdio-ui5-servicev3.0.12
Functional boundary

End-to-end testing for UI5 on WebdriverIO with UI5 control selectors

Details

History4
  • ui5-test-runnerdescription.what_it_solves → Four automation libraries are documented, `puppeteer` by default plus `playwright`, `selenium-webdriver` and `webdriverio`, each with the browsers it can launch, and version 6 states that JSDOM browser emulation is no longer supported.The sentence was read on 2026-09-30 and version 6 changed it: the breaking-changes page states JSDOM browser emulation is no more supported, and the browser-selection page now names four libraries, with the browser chosen by a separate option. The clause about libraries being fetched during the run was dropped from this sentence because it is the same claim as the pitfall recorded under agent, which the v6 dependency pages were not read for.
  • ui5-test-runnerprovides[capability:ui5-testing].sources → docs/introduction.md and docs/browser_selection.mdThe usage page cited on 2026-09-30 is not in the docs folder today; the pages that carry the same statements in version 6 are the introduction and the browser-selection page, both read on 2026-10-15.
  • ui5-test-runnerprovides[capability:ui5-testing].facets → test_level, coverage_reportBoth are stated by the documentation in its own words: QUnit pages are labelled unit tests and OPA5 pages integration tests, and coverage is documented for both modes. Version 6 turns coverage off by default, which is a setting and not a change to whether it is available.
  • First entry seenDiscovered via Added by hand.
Profile1
For your agent