SAPFX

Business-readable SAP tests, three channels, no license.

Open source · Apache 2.0 · Robot Framework

Automating SAP means juggling two worlds that have nothing in common: the SAP GUI desktop client and the Fiori web. Two tools, two skill sets, and tests that break at the slightest change of screen, id or language. Maintenance ends up costing more than writing.

At a glance

What: SAPFX (PyPI distribution robotframework-sapfx), an open-source SAP test automation ecosystem for Robot Framework.
Channels: SAP GUI desktop (ECC, S/4HANA), Fiori/SAPUI5 web (UI5 1.60 to 2.0), OData v2/v4 and RFC APIs.
Differentiators: business-readable tests with no technical identifiers, logged locator self-healing, AI agents (plan, generate, heal) over MCP.
License: Apache 2.0, zero fees; code on GitHub, package on PyPI.
Proof points (v0.6.5, August 2026): 1016 unit tests, 17/17 scenarios validated against a real SAP system, 93% measured coverage.

The idea

Write the test once, in business language. The same keyword works on the SAP GUI, on Fiori or through the OData API. Underneath, three Robot Framework libraries (SapEccLibrary, SapFioriLibrary, SapApiLibrary) and machinery built not to break for the wrong reasons: waits track the real SAP state, assertions are language-independent, locator self-healing is always logged.

Go To Transaction    VA01           # SAP GUI
Open App             Sales Order    # Fiori

The project on video

Project overview: three channels, self-healing, AI agents (French narration).

What it does

One vocabulary, three channels. The same test reads identically whether it drives the GUI, Fiori or the API.
Tests that do not break for nothing. Real SAP waits, language-independent assertions, no technical identifiers in the tests.
AI-native, under control. Agents plan, write and repair tests by driving the real system; every generated step is executed live before being written.
Maintenance becomes preventive. Screen drift sentinel, visual assertions, telemetry of drifting locators.
Commercial-suite capabilities, open-source cost. No license, no vendor lock-in.

Live, not on slides

Live self-healing: a locator drifts, the test repairs itself, everything is logged.

SAP GUI recorder: a real flow becomes a replayable Robot Framework suite.

Fiori web recorder: recording on a real Fiori Elements app, replay and export.

Proof, not promises

1016 unit tests, replayable without SAP

17/17 scenarios validated against a real SAP

3 channels: GUI, Fiori, API

€0 license fees (Apache 2.0)

Figures observed at version 0.6.5 (August 2026). Measured coverage: 93%, CI floor: 85%. UI5 compatibility proven from 1.60 to 2.0. Bilingual French/English documentation.

Where it stands

Commercial SAP testing suites are mature and complete, with vendor support and a codeless mode that SAPFX does not have; their licenses run from tens to hundreds of thousands of euros per year. The historical open source is single-channel: RoboSAPiens covers the SAP GUI only, wdi5 the UI5 web only, outside Robot Framework. SAPFX covers all three channels inside Robot Framework, with a single report, for free.

Comparison matrix: SAP GUI, Fiori, API coverage and self-healing of SAPFX versus commercial suites and single-channel open source (in French) — An indicative market reading, not a funded benchmark (matrix in French).

Try it

pip install robotframework-sapfx

Or the standalone Windows pack shipped with every release: one-command install, no repository clone. The Fiori side can be tested without any SAP system; the SAP GUI side is validated against the free ABAP Platform Trial in Docker.

Source code (GitHub) PyPI package

The SAPFX frequently asked questions live on the site's FAQ page.

Contact: