Complete guide to install and configure every code quality, documentation, security, and standards enforcement tool used in Praman — TypeScript strict mode, ESLint with 13 plugins, Vitest tiered coverage, security scanning, SBOM generation, and CI pipeline scripts. Includes a one-shot install command.
Prerequisites: Node.js >= 22, npm >= 10, Git.
Praman v1.3 is CI-tested on Node.js 22, 24, and 26 across three operating systems, ships published types compiled with TypeScript 6.0.3, validates against TS 5.9 and TS 6.0 on every push, and passes a clean typecheck against the TypeScript 7.0 beta (tsgo). This post documents the evidence behind each compatibility claim so your team can adopt Praman with confidence.
When your SAP Center of Excellence evaluates an open-source testing library, the feature list is necessary but not sufficient. You need to trust the engineering behind it. Can you hand this dependency to your security team and get sign-off? Will it still build cleanly in three years when your SAP landscape has moved through five transport cycles? Does the project have governance, or is it held together by convention and good intentions?
Praman ships with 22 quality tools and 13 ESLint plugins enforced on every commit, every push, and every CI run. Zero warnings allowed. No exceptions. This post walks through every one of them — with exact versions, configurations, and thresholds from the actual project — so you can evaluate the engineering standard before you evaluate the feature set.
Your SAP landscape has 200+ Fiori apps, quarterly transport cycles that break tests, and a test automation backlog measured in person-years. You have heard the pitch: AI-first test automation for SAP UI5. But before committing budget, headcount, and political capital, you need proof.
This guide is the POC playbook. It covers the 9 hardest scenarios that separate SAP test automation tools from SAP test automation solutions — and gives you exact steps, agent commands, code, and scoring criteria to evaluate Playwright-Praman in your own landscape.
Praman 1.3.0 is now available on npm. This release brings Playwright 1.60 support with 8 new feature flags, TypeScript 7.x compatibility, AI grounding via full-page ARIA snapshots, a screencast control highlighting fixture, the ESLint 10 toolchain upgrade, and an expanded docs verification pipeline with 8 automated checks.
SAP test automation has always been hard. The controls are deep, the IDs are long, the events are complex, and every app behaves differently depending on whether it's V2 Smart or V4 MDC. The Praman CLI agents showed that AI agents could handle this complexity — but they required copying agent markdown files into every project and manually enforcing compliance rules.
Today we're releasing two plugins that change that — one for Claude Code and one for Claude Cowork. Same 5-agent pipeline, same compliance rules, two interfaces.
# Claude Code — CLI
claude plugin marketplace add mrkanitkar/praman-sap-testing
claude plugin install praman-sap-testing@praman-sap-testing
# Claude Cowork — Customize → Browse plugins → Install
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.57+, TypeScript 6.x & 5.x, Praman CLI Agents, Praman MCP Agents, a completely rewritten ui5= selector engine, a live interactive inspector,
OpenTelemetry tracing & metrics, and a battery of quality-of-life improvements for teams building SAP UI5 test automation at scale.
A structured, prompt-engineered template for AI agents to automate the complete SAP Sales Order lifecycle — from order creation through delivery, picking, goods issue, and billing — using Praman fixtures and OData-first selectors.