3 posts tagged with "CLI"

Praman ships two variants of its SAP test agents: MCP agents that communicate through a WebSocket-based MCP server, and CLI agents that use playwright-cli over stdin/stdout. This post walks through the CLI variant end-to-end, based on a real session testing a "Maintain Bill of Material (Version 2)" app on SAP S/4HANA Cloud. The session required 8 iterations to get a passing test, and the debugging process revealed important patterns around FLP navigation, dialog handling, and V4 Fiori Elements ID structures that apply to any SAP testing project.

Testing SAP S/4HANA and Fiori apps at enterprise scale requires more than a browser automation library. You need UI5-aware selectors, authentication handling, OData support, and — increasingly — agentic AI workflows that can plan, generate, and self-heal tests. Four open source solutions tackle this problem from different angles.

This post compares playwright-ui5, playwright-sap, wdi5, and playwright-praman side by side. No marketing. Just what each tool actually does, where it falls short, and which one fits your situation.

Legend: ✓ = Full support | ✓+ = Enhanced/extra features | ⚠ = Partial/limited | ✗ = Not supported

We are releasing Praman 1.2.0 to the latest tag on npm today. This is the largest functional update since the v1.0 launch, bringing first-class support for Playwright 1.59, TypeScript 6.x, a completely rewritten ui5= selector engine, a live interactive inspector, and a battery of quality-of-life improvements for teams building SAP UI5 test automation at scale.