UI5 testing
Proving 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.
Showing artifacts, examples and content with confirmed Web Components applicability. View All UI5
Overview
UI5 Web Components have no controller, view or control tree for QUnit and OPA5 to test: the library describes itself as usable with any current or future web development framework rather than built on the OpenUI5 runtime. wdi5, the community's end-to-end framework for UI5 apps, defines its own locators as something that identifies a UI5 control to retrieve and use for further test work, which a Web Components app has none of.
Artifacts
Nothing is mapped here yet.
Details
Coverage
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:ui5-testing- JSON
- /capabilities/ui5-testing.json
- MCP
- Connecting an agent