SAP test automation · Robot Framework

Test SAP end to end, keyword by keyword

Three channels, the same contracts: SAP GUI, Fiori/UI5 and OData API. These pages are the complete keyword reference of the three libraries shipped on PyPI and of their shared modules, generated with Libdoc from the released code.

Apache 2.0 Robot Framework 7 pip install robotframework-sapfx
SAPFX: ECC UI5 API Library
Keyword reference · three channels

Three libraries, shared rules

SapEccLibrary

Desktop channel · SAP GUI (ECC, S/4HANA)

Drives SAP GUI for Windows through the SAP GUI Scripting API. Screen perception, label-based locators, self-healing locators, multi-session, visual assertions.

Open the keyword reference →

SapFioriLibrary

Web channel · Fiori / SAPUI5

Fiori automation on top of the Browser library (Playwright). Five resolution engines (UI5 controls, hierarchical XPath, WebGUI, Web Components, generic DOM), launchpad iframes, aggregated diagnostics.

Open the keyword reference →

SapApiLibrary

API channel · OData v2/v4 and RFC

The screenless channel: OData reads and writes (CSRF, atomic $batch, pagination), reversible test-data factory, Gateway preflight, and the BAPI pattern on top of optional RFC.

Open the keyword reference →

sapfx_common

Shared modules · imported one by one

The channel-independent keywords that chain after any channel: table extraction and its completeness guard, exports (CSV, JSON, Excel, SVG, Parquet), deterministic artifacts, cross-channel checks, security posture, change impact, release verdict.

Open the keyword reference →
These pages document the keywords of the libraries. A test suite usually calls them through a layer of business keywords (one resource file per screen or flow), so that tests contain no raw locators; the sapfx_common modules are how that layer reaches pure logic without Evaluate.