Updated August 21, 2026
Support matrix
Start here if you need to know whether your UI or API can run automated tests on Velo.
| Client | Kind | Remote in Velo | Engines | Status |
|---|---|---|---|---|
| Web (Chromium, Firefox, WebKit) | UI | Yes | Robot Framework (robot-web), Playwright (playwright) | Supported |
| SAP GUI for Java | UI | Yes (Linux container) | Robot Framework (robot-sap) | Supported |
| SAP GUI for Windows | UI | No — local / debug only | Robot Framework (client=windows) | Supported locally. Remote uses Java. |
| SAP Fiori | UI | — | Will use Web | Planned |
| REST / HTTP APIs | Headless | — | k6, Locust | Planned |
How to read it
- Client — the app surface. If it is not listed as supported, Velo cannot open that session remotely.
- Kind — UI clients need a display (and usually video). Headless clients do not.
- Remote — a managed container on Velo. Local / debug runs on the tester's machine with the native client.
- Engine — the script runner that implements the client. The dashboard
enginefield is the image ID in parentheses, not the engine name.
SAP GUI for Windows and SAP GUI for Java share the Robot keyword surface (VeloSapguiLibrary). A suite authored on Windows still runs remotely when it stays on that surface and the image is robot-sap (Java in the container). Set VELO_SAP_CLIENT=java or leave auto off Windows.
Engine → client
| Engine | Clients it can drive |
|---|---|
| Robot Framework | SAP GUI Java, SAP GUI Windows, Web |
| Playwright | Web |
| k6 / Locust | Headless REST (planned) |