Automating SAP Fiori and UI5 Applications

Keep this: job aid

Fiori and UI5 automation checklist

• Locate controls by selector (view plus stable ID, or control type with binding path, label or i18n text), never by __generated IDs, XPath or pixels.
• Open the Test Recorder (Ctrl+Shift+Alt+T) to inspect control type, ID and bindings; confirm each selector matches exactly one control.
• Push detail down: formatters and logic in QUnit, single-app behavior in OPA5 with the mock server, end-to-end only for processes.
• Wait for conditions, not time: UI5 idle (requests, timers, promises, navigation) plus control visible, enabled and not busy.
• Handle toasts, busy-state checks and draft saves deliberately; log selector, expected state and last observed state on timeout.
• Start most scripts by intent; keep a few tile-click journeys per business role; run as role-based test users, never a super user.
• Pin window size and theme for regression; assert on bound values and messages, not colors, classes or positions.
• For custom apps: stable semantic IDs (no hyphens), Support Assistant stable-ID rule clean, ID changes reviewed as breaking changes.
• Record user, role, app ID and UI5 version with every run as sign-off evidence.