Playwright
A library that drives Chromium, Firefox and WebKit from code, written for end-to-end browser testing. For the things here it is the browser a tool starts itself, to get through an SAP login or to load a page headless and photograph it.
Where it sits
Used by
Optionally used: the render gate or --screenshot is used the headless Chromium the render gate loads the view in: that gate is a second install, @abap2ui5/linter-render plus npx playwright install chromium, and the property gate runs in full without it
Functional boundary
Event roundtrips and visual fidelity stay with a live run: the documentation leaves those to the project's MCP server and to [abap2UI5 for VS Code](artifact:abap2ui5-vscode-extension). A class that builds view parts in helper methods without the handle idiom cannot be statically reconstructed, and the render gate is then skipped with a notice while the property gate runs on what was reconstructed. A screenshot is not a preview of the app: nothing round-trips, no event reaches ABAP, and a table filled by a SELECT photographs empty unless a mock JSON file sits beside the source.
Optionally used: A tool that renders or boots in a browser is used: screenshot_view, run_app or interact_app The browser the reconstructed view is rendered in and the app is booted in; A2UI5_MCP_CHROMIUM or a system chromium can stand in for the Playwright-managed one.
Functional boundary
Every gate here runs off-system, so what the class does on a real system and what the view does on the oldest UI5 release it has to serve are what the `pitfalls` catalogues carry and no local run can see. It runs abap2UI5 app classes, so ABAP that is not one has nothing here to deploy into. In system mode the sandbox tools are not offered, and an `app_act` event runs on the system as the configured user.
Required dependency. The browser it drives through the SAP login page, installed by the caller rather than bundled, so the project decides which browsers are downloaded.
Functional boundary
The maintainer states it is unofficial, not endorsed by SAP, and that it automates authenticated SAP web endpoints and browser session cookies in ways SAP's terms of service or an organisation's own policies may restrict. Password login is confined to `accounts.sap.com` and the standard SAP Cloud Identity Services tenant domains: a custom IAS domain, or a login that conditional authentication delegates to a corporate identity provider, fails closed before the password is filled and has to be completed through an interactive login instead.
Required dependency. to install Chromium for the authenticated MCP servers (API Hub, Roadmap, Notes) this skill requires evidence from
Functional boundary
It says so itself, in bold, and the atlas repeats it: not legal advice and not a compliance decision. Only SAP, your contract, or SAP support can answer bindingly, and the skill routes legal, commercial and roadmap questions there rather than guessing at them. Treat the output as evidence gathered, not as a verdict.
Details
Graph
For your agent
- Ref
external:playwright- JSON
- /externals/playwright.json
- MCP
- Connecting an agent