There are no items in your cart
Add More
Add More
| Item Details | Price | ||
|---|---|---|---|
See how an AI agent can read plain-English test cases, drive a real browser on a Fiori-style SAP app, and catch regressions with screenshot evidence.
Wed Nov 18, 2026
Regression testing is the part of every SAP release that everyone agrees matters and nobody has enough time for. Scripts break when the UI changes. Manual runs get squeezed into the last two days before a transport goes to production. And the test cases that do exist often live in a spreadsheet nobody has opened since UAT.
AI agents offer a different approach. Instead of writing a brittle script for each scenario, you write the test case the way a functional consultant already would, in plain English, and an agent works out how to run it in the browser.
This post explains how that works, what it looks like on a Fiori-style Sales Orders app, and where the limits are.
The setup has three parts:
The important shift is that the test case is the source of truth, not the script. If a button moves, the agent still finds it, because it reads the page the way a person would.
Imagine a Fiori-style Sales Orders app built on OpenUI5, with a few business rules taken from a functional spec:
You write eight test cases from that spec. Two of them are a boundary pair:
Now a new release goes out, and a developer accidentally changes the discount threshold logic.
When the agent runs the suite:
That pattern is exactly what a good tester looks for: the boundary moved. The agent saves a screenshot of the order screen and a JSON report with the expected and actual values, so a developer can see the problem in seconds.
The agent is only as good as the test cases you give it. In practice:
AI makes running tests cheaper. It doesn't replace good test design. If anything, it rewards consultants who already write clear specs.
An agent that can click anything in a browser needs firm limits, especially near business systems:
The common mistake is to treat the prompt as the security control. The prompt asks for good behaviour. The guardrails enforce it.
A useful agent reports two different kinds of "not passed":
Keeping these separate stops your team from chasing false alarms.
It won't replace your test management tool, and it isn't a substitute for an enterprise automation suite on a large programme. But for a functional consultant who wants to understand and demonstrate AI testing, it's the fastest way to get hands-on.
Our Lab 3: AI Agent That Tests a Fiori-Style SAP App walks you through the whole build on your own Google Cloud project, in 7 modules:
It has a 17-page guide and a capstone where you write your own test case. Every step is checked before you move on.
Not affiliated with or endorsed by SAP SE or Google. The app, data and customers in the lab are synthetic.