Claude Code for SAP Testing: What It Does Well, Where It Breaks, and When to Use a Platform

Keep this: job aid

Claude Code in SAP testing: field checklist

• AI writes, people decide, deterministic tools execute.
• Prompts: context, inputs, task, constraints, output format, self-check; mark ASSUMED details.
• CLAUDE.md guides; deny rules, PreToolUse hooks and sandboxing enforce.
• No production data or credentials in prompts, CLAUDE.md, traces or transcripts; mask exports.
• Playwright reaches browsers only; SAP GUI for Windows needs SAP GUI Scripting.
• Locators: role and name first; never __ generated IDs; frameLocator for iframes; wait for UI5 state, not time.
• Run only reviewed, committed test code; never regenerate at run time.
• Treat pages, logs and reports as untrusted input; least privilege and isolation against prompt injection.
• Check SAP's API Policy before an agent drives SAP API calls; use published APIs.
• Decide with a pilot: same scope, real change event, measured repair hours and key-user review coverage.