Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 5 of 5

Reporting Fiori defects

9 min

Listen to this lesson

0:00 / 18:20

A Fiori defect that says "the purchase order app doesn't work" can cost a developer a day. Which app? Which version? Which role? Which browser? Many Fiori apps look alike, several versions of an app can coexist, and behavior depends on role content, device and personal settings. A good Fiori defect carries that context from the start.

The required context

FieldWhere to get itWhy it matters
App name and app IDAbout dialog; SAP Fiori apps reference libraryPinpoints the exact app and its technical components
App version and SAPUI5 versionAbout dialogBehavior and fixes differ by version
Application componentAbout dialog (current releases) or reference libraryRoutes the defect to the right team or SAP component
Test user and business roleTest case; user's role assignmentVisibility and authorization depend on role
Launchpad URL or intentBrowser address bar (the part after #)Shows exactly which app and parameters were started
Browser, version, device, screen size, themeBrowser settings; the About dialog's user agent detailsRendering and touch issues are combination-specific
Steps, data, expected and actual resultTest case and executionMakes the defect reproducible
Messages with their detailsMessage popover or dialog, including technical details where shownBackend message IDs point to the code that raised them

Context every Fiori defect should carry.

Technical helpers

SAPUI5 includes diagnostic tools that testers can open with keyboard shortcuts: Ctrl+Alt+Shift+P shows technical information about the running app and framework, and Ctrl+Alt+Shift+S opens the UI5 Support Assistant or diagnostics, depending on version. You do not need to interpret everything they show, but a copy of the technical information attached to the defect saves a round trip. For errors that come from the backend, support can search the SAP Gateway error log for the user and time you record. Your project may also ask for a browser network trace for hard cases; follow its guidance on what may be shared, because traces can contain personal data.

Classify each defect as you log it. A function defect is wrong business behavior in any UI. A content and role defect is about what a role can see or reach. A pattern defect concerns drafts, filters, variants or messages. A device defect appears only on certain browsers, screens or input methods. An accessibility defect blocks users of assistive technology. Each class goes to a different team, so a correct class saves a hand-off.

Defect classTypical Contoso exampleUsually routed to
FunctionWrong price on an order for Great Lakes Fleet Services, in any UIFunctional configuration or development
Content and roleChicago buyer cannot navigate from PO to supplierSecurity or launchpad content admin
PatternDraft lost, variant not restored, save fails silentlyApp development or support
DevicePost action unreachable on the warehouse tablet in portraitUI development, with the device and browser recorded
AccessibilityError announced only by red colorUI development against the accessibility policy
Classifying a Fiori defect correctly sends it straight to the team that can fix it.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-208
  1. ReproduceRepeat with a clean test user and note the exact steps and data
  2. IdentifyAbout dialog: app ID, version, SAPUI5 version, component
  3. ContextUser, role, URL or intent, browser, device, theme
  4. EvidenceMessages with details, screenshot with personal data masked, technical info
  5. ClassifyFunction, content and role, pattern, device, or accessibility
From observation to a complete Fiori defect.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-208

Practice: two Contoso defects

Launchpad contentVerified per business role with a clean test user.
Critical apps through savePosting results checked, with draft, filter, variant and message pattern checks.
Browsers and devicesThe agreed combinations from the coverage matrix, such as Edge on laptops and Chrome on Chicago tablets.
AccessibilityA basic pass on every critical app.
Open defectsListed with app ID and role, so the process owner knows exactly what remains.
The evidence a process owner should see, per business role, before signing off a Fiori release.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-208

What would you do?

A key user writes: "Invoice app crashes, please fix ASAP." Contoso has three supplier invoice apps in use. What should the tester add first?

Key points
  • Every Fiori defect needs app name, app ID, app and SAPUI5 versions, and application component.
  • Add the user and role, URL or intent, browser, device, screen size and theme.
  • Use the About dialog and SAPUI5 diagnostics; backend errors can be traced in the Gateway error log.
  • Classify defects as function, content and role, pattern, device or accessibility to route them quickly.

Check your understanding · not graded

Lesson check

  1. 1. Why should a Fiori defect include the app ID?

  2. 2. Which keyboard shortcut shows SAPUI5 technical information for the running app?

  3. 3. Why record the launchpad URL or intent in a defect?

  4. 4. A navigation link works for a broad role but not for a business role. How should the defect be classified?