ZeuZ
SAP test automation

SAP test automation for S/4HANA, Fiori and SAP GUI.

SAP test automation in ZeuZ covers Fiori apps in the browser, SAP GUI for Windows on the desktop and OData services over the API, in one suite with the non-SAP systems around them. Describe the transaction in plain English; ZeuZ writes it, runs it before the transport moves and repairs what the upgrade changed.

S/4HANAFioriSAP GUI for WindowsODataOn-premisesAir-gapped
node-toronto-01atlas-crmrelease/2026.09
Test case · Create sales order VA01 and confirm delivery
Passed
3 / 3
Steps passed
3
Surfaces
2m 41s
Duration
BrowserFiori launchpad · Create Sales Order✓ Passed
Chrome · app F3893 opened, order 4501277 created
WindowsSAP GUI for Windows · post delivery✓ Passed
located by AutomationId "btnPostDelivery" · UI Automation API
APIOData GET · assert order status✓ Passed
GET /SalesOrder('4501277') → Status: Delivery confirmed · 200 OK
Run on node-toronto-01 · inside your networkrelease/2026.09
In one paragraph

SAP test automation is the automated re-testing of SAP transactions, Fiori apps, OData services and integrations after a transport, a support pack or an S/4HANA upgrade, so business processes keep working when the system changes. ZeuZ automates SAP across all three surfaces, Fiori in the browser, SAP GUI on Windows and OData over the API, and runs inside your own network where SAP shops require it.

Part of ZeuZ Test Studio · Fiori in the browser, SAP GUI for Windows on the desktop, OData over the API, plus the web, desktop, API and database systems around them
The problem

Where SAP testing breaks today.

A quarterly transport touches dozens of transactions and the regression pack is run manually by the people who also run the business.

SAP GUI is a Windows application, Fiori is a browser application and OData is an API, so three tools and three teams own one process.

Nothing with production-like data may leave the network, which rules out most SaaS testing tools before the evaluation starts.

The six steps

How ZeuZ automates SAP test automation.

  1. 01Test designProposes the transactions and Fiori apps a transport touches, ranked by process impact, from the change list and tickets.
  2. 02Test case creationA functional consultant describes the transaction in plain English; ZeuZ writes the case with reusable steps for logon, navigation and posting.
  3. 03Test automationFiori through the browser, SAP GUI for Windows through Windows UI Automation with image and OCR fallback, OData through REST actions, in one case.
  4. 04Test executionRuns before the transport moves and after it lands, on a schedule or a pipeline webhook, on nodes inside your network.
  5. 05Reporting and analysisEach failed step returns the exact screen, error and trace, pinned to the transport or release that produced it.
  6. 06Test maintenanceWhen an upgrade moves a field or a Fiori control, ZeuZ proposes the repair as a diff a person approves.

Your team reviews what ZeuZ produced. Nothing joins the suite or runs without a person accepting it.

See it in the demo lab or in your own environment

See it run on your application.

Watch a Fiori, SAP GUI and OData step run together in one test case.

What is covered

SAP testing tools for all three surfaces.

ZeuZ reaches SAP on every surface a process runs on. Fiori and SAP GUI for HTML run in the browser on Chrome, Firefox, Edge and Safari, with partial-match locators for generated IDs. SAP GUI for Windows runs through Windows desktop automation on Windows 7 through 11: elements are located by Name, Class, AutomationId and ControlType through the UI Automation API, by element path, or by image and OCR where a control exposes nothing, with keystrokes for transaction codes and function keys. OData services are tested through REST actions with authorization headers, JSON schema validation and deep response extraction.

The non-SAP systems in the same process, a web portal, a Windows client, a database, an IDoc-driven integration checked through its API, run in the same test case. SAP test automation in ZeuZ deploys on-premises or air-gapped where SAP shops require it, and the evidence for every surface stays on one record.

Fiori
Browser automation, Chrome, Firefox, Edge, Safari
SAP GUI for Windows
UI Automation API, element path, image, OCR
OData
REST actions, auth, schema validation, extraction
Deployment
SaaS, on-premises, air-gapped
Surrounding systems
Web, desktop, API, database in one case
Evidence
Screen, error and trace per step
VA01ME21NMIGOFiori launchpadOData v2/v4Transport-triggered runs

Runs where your code is allowed to be.

SaaS

Hosted by ZeuZ, execution on your own machines.

On-premises

Point the client at your own server.

Air-gapped

Disconnected environments, scoped per engagement.

Runs inside Jenkins, GitHub Actions, Azure DevOps, CircleCI and Bitbucket; results into Jira, Slack and Teams.

Related capabilities

Works in the same suite as.

Desktop application testing

Windows and macOS applications automated through the same UI Automation, element path, image and OCR detection SAP GUI uses.

Desktop application testing →
API test automation

REST, SOAP and GraphQL services tested with auth, schema validation and response extraction, in the same cases as the UI.

API test automation →
Automated regression testing

The full suite on every merge or transport, with locator breaks returned as proposed repairs a person approves.

Automated regression testing →

Read next: Deployment options →

FAQ

Questions about SAP test automation.

What is SAP testing?

+

SAP testing is the verification that SAP transactions, Fiori apps and integrations still work after a change: a transport, a support pack or an S/4HANA upgrade. It spans three surfaces, Fiori in the browser, SAP GUI on the desktop and OData over the API, plus the non-SAP systems in the same business process. ZeuZ automates all three surfaces in one suite, with each run's screens, errors and traces on one record.

Try ZeuZ Free →

How do you regression test an S/4HANA upgrade?

+

Re-run automated cases for the transactions and Fiori apps the upgrade touches, before the change moves and after it lands, and compare the evidence per step. The suite has to cover Fiori, SAP GUI and OData together or the gap simply moves. ZeuZ proposes the cases a transport touches from the change list, runs them on nodes inside your network, and when the upgrade moves a field or a Fiori control, proposes the repair as a diff a person approves.

Automated regression testing →

How do you test an OData service in SAP?

+

Call the service with authorization headers, validate the response against a JSON schema and assert the values the process depends on. ZeuZ tests OData v2 and v4 through REST actions with deep response extraction, and puts the API assertion in the same test case as the Fiori or SAP GUI steps that produced the data, so a wrong order status is traced to the exact step that broke it.

API test automation →

Can one suite cover SAP and the non-SAP systems around it?

+

Yes, when the tool automates web, desktop, API and database in one case rather than one tool per surface. A single ZeuZ case can post a transaction in SAP GUI for Windows, confirm it in a Fiori app, check the OData response and verify the surrounding web portal or database, with each step's screen, error and trace on one record. Most tools automate one surface and leave the rest of the process to people.

Try ZeuZ Free →

Can SAP test automation run inside our own network?

+

Yes. ZeuZ deploys as SaaS, on-premises or air-gapped, and execution always runs on nodes you control, so production-like SAP data never leaves the network. That fits SAP shops in banking, energy, insurance and government, where cloud-only testing tools are ruled out before the evaluation starts. Runs start on a schedule or from a pipeline webhook inside Jenkins, GitHub Actions, Azure DevOps, CircleCI or Bitbucket.

Deployment options →

Ready to automate QA testing today?

See ZeuZ Test Studio write, run and repair tests against your own application code.

or explore our services →
Try ZeuZ Free