Question 1

What SAP systems does Praman support?

Accepted Answer

Praman supports SAP S/4HANA (on-premise and cloud), SAP BTP applications, SAP Fiori Launchpad, and any web application built with SAPUI5 or OpenUI5. It works with both SAP Fiori Elements and custom UI5 freestyle apps.

Question 2

Do I need access to SAP source code to use Praman?

Accepted Answer

No. Praman interacts with UI5 controls through the public runtime API (sap.ui.getCore()). It queries the control registry at runtime, so you only need browser access to the application.

Question 3

Can I use Praman with existing Playwright tests?

Accepted Answer

Yes. Praman extends Playwright — it does not replace it. You can mix Praman fixtures (ui5, ui5Navigation, ui5Table) with native Playwright APIs (page.click(), page.locator()) in the same test file.

Question 4

How does Praman compare to wdi5?

Accepted Answer

Both access the UI5 control registry. Praman is built on Playwright (faster, modern), while wdi5 uses WebdriverIO. Praman adds typed control proxies with full IntelliSense, AI-powered test generation, Fiori Elements page-object helpers, OData V2/V4 mock/intercept utilities, and 10 UI5-specific Playwright matchers.

Question 5

How does AI test generation work in Praman?

Accepted Answer

Praman integrates with AI coding agents (Claude Code, GitHub Copilot, Cursor, Jules). You describe what to test in business language, and the agent generates production-ready Playwright tests using Praman fixtures with typed control proxies — not brittle selectors.

Question 6

What authentication methods does Praman support for SAP?

Accepted Answer

Praman supports 6 authentication strategies: BTP SAML, Basic Auth, Office 365, Client Certificate, Custom IDP, and Manual login. Authentication is handled in seed tests and sessions are reused across test runs.

Question 7

How many SAP UI5 controls does Praman support?

Accepted Answer

Praman supports 199 UI5 control types across 8 SAP libraries: sap.m, sap.ui.table, sap.ui.comp, sap.uxap, sap.f, sap.ui.mdc, sap.ui.unified, and sap.ui.core. Each control type has a fully typed proxy with IntelliSense.

Question 8

Is Praman free and open source?

Accepted Answer

Yes. Praman is licensed under Apache-2.0 and is completely free. It has only 3 production dependencies (commander, pino, zod), all MIT-licensed. The source code is available on GitHub.

Question 9

How does Praman compare to Playwright-SAP?

Accepted Answer

Both extend Playwright for SAP testing. Praman provides 199 typed UI5 control proxies with IntelliSense, AI-powered test generation via coding agents, OData V2/V4 testing utilities, Fiori Elements page-object helpers, 6 SAP auth strategies, and 10 custom matchers. Playwright-SAP provides SAP-aware locators (getByRoleUI5, locateSID) and auto-login helpers. Praman is a deeper plugin with fixtures and AI; Playwright-SAP is a lighter locator extension.

Question 10

Is Praman an alternative to Tricentis Tosca for SAP testing?

Accepted Answer

Yes. Praman is a free, open-source alternative to Tricentis Tosca and Worksoft for SAP S/4HANA testing. It uses Playwright (78,000+ GitHub stars) as its engine and adds AI-powered test generation, typed UI5 proxies, and SAP-specific fixtures. Unlike Tricentis, there are no license costs, no vendor lock-in, and tests are standard TypeScript.

Question 11

Does Praman support SAP S/4HANA migration testing?

Accepted Answer

Yes. Praman is designed for SAP RISE, public cloud, and on-premise S/4HANA migration testing. It supports greenfield, brownfield, and bluefield deployment models. Features include behavioral equivalence testing (ECC vs S/4HANA), data integrity validation, business flow performance heatmaps, and compliance reporting for migration cutover.

Question 12

Can Praman test SAP Fiori Launchpad and Fiori Elements apps?

Accepted Answer

Yes. Praman provides dedicated fixtures for SAP Fiori Launchpad navigation (9 methods including semantic object routing and BTP WorkZone support) and Fiori Elements page-object helpers for List Report, Object Page, and Overview Page. It handles tile navigation, intent-based routing, and FLP shell interactions natively.

Interface: SectionLinkNavigationOptions

Example

Properties

timeout?

waitForStable?

Example​

Properties​

timeout?​

waitForStable?​

Example

Properties

timeout?

waitForStable?