Architecture
Functional Architecture
AI@Test follows a closed-loop architecture: the AI agent issues instructions to SAP through a protocol layer, reads back the result, and either validates success or initiates a self-healing correction — repeating until the test step passes or a defect is logged.
🔍 CLICK TO ENLARGE
When the AI Resolution step produces a correction, the loop restarts from the MCP Layer with the corrected action — up to the configured number of retry iterations. When a step passes, the agent advances to the next test step.
Prerequisites
For SAP GUI Desktop automation
| Requirement | Details |
|---|---|
| Operating system | Windows only (COM scripting is a Windows-only technology) |
| SAP GUI version | SAP GUI 7.60 or higher with SAP GUI Scripting enabled |
| Scripting activation | In SAP GUI: Options → Accessibility & Scripting → Scripting → Enable scripting |
| BASIS approval | SAP GUI scripting is disabled by default in most corporate landscapes — BASIS team must enable it at system and user level |
| Active session | SAP GUI must be open and logged into the target system before the agent starts |
| sap-bridge running | The AI@Test bridge service must be running on the same Windows machine as SAP GUI |
SAP GUI automation requires a visible desktop session. It cannot run headless or in a Linux container. For CI/CD pipelines, use a Windows-based runner with a permanent SAP GUI session or connect to a Citrix / RDP session.
For SAP Fiori automation
| Requirement | Details |
|---|---|
| Browser | Google Chrome (recommended) or Microsoft Edge — Chromium-based browsers only |
| SAP Fiori Launchpad | The target Fiori Launchpad must be accessible via HTTPS from the agent machine |
| User credentials | A test user with the necessary Fiori authorizations for the applications under test |
| Network access | The agent machine must have HTTP/HTTPS access to the SAP Fiori frontend server |
| Browser automation | Chrome DevTools Protocol (CDP) is used — no browser extension required |
| Fiori app compatibility | Supports SAP UI5-based Fiori apps (freestyle, List Report, Object Page patterns). Custom non-UI5 apps require case-by-case assessment |
For Fiori testing, a headless Chrome instance can be used, making it compatible with Linux-based CI/CD environments such as GitHub Actions or Azure DevOps.
Integration with AI@KB
When an AI@KB system report is available for the target SAP system, AI@Test can use it to design test cases grounded in the actual system configuration:
- Document types, delivery types, billing types, and pricing conditions are read from the AI@KB extract
- Test cases are tailored to the specific variant configured in your system — not generic templates
- Transactional data volumes and active configuration objects inform which test paths are relevant
This integration significantly reduces the time to produce a meaningful end-to-end test suite at the start of a project or before a major system change.