Automation Framework Design for SAP Landscapes

Keep this: job aid

SAP automation framework design card

• Three layers: business-readable test definitions → business components → technical adapters and core libraries. Tests never call adapters.
• Cover the gTAA capabilities: definition, execution, adaptation (generation optional); plan interfaces to SUT, project, test and configuration management.
• Components: one recognizable SAP business transaction; documented inputs, outputs, pre- and postconditions; return document numbers; no assertions inside.
• Same component, different modes: through the UI for the user path, through a released API for setup.
• Keywords (ISO/IEC/IEEE 29119-5): business-level keywords in tests, technical keywords hidden; one owner governs the catalog.
• Externalize systems, clients, users, data and run settings; secrets in a credential store; validate the profile at run start.
• Map every automated test to a test case in SAP Cloud ALM; publish status and evidence through the test automation API.
• Evidence: business document numbers, step log, screenshots or request/response, full context, failure detail.
• Route failures: product defect, test defect, data or environment; deduplicate by signature; link defects and retests.
• Review each release for coupling, duplication and readability; measure repair hours, files touched per change and flaky rate.