Test Design Techniques Applied to SAP Transactions and Fiori Apps

Keep this: job aid

SAP test design card

• Limit, threshold or quantity → partitions plus boundary values; neighbor = field precision (one cent, one piece, one day).
• Financially sensitive limit → three-value boundaries: just below, at, just above.
• Several conditions decide an outcome → decision table; list every combination before collapsing.
• Look for missing rules (nothing determined) and conflicting rules (row order decides the winner).
• Statuses, approvals, blocks → state table; attempt every refused transition to prove the control.
• Include changes after release, threshold-crossing edits and partial processing states.
• Weak spec or fragile area → time-boxed charters and the fault list (dates, currencies, rounding, units), then formalize.
• Reset test data between boundary tests: exposure, open items and released documents change the starting state.
• Record in every test case: rule ID, technique, model, coverage items, coverage achieved, agreed exclusions.
• Sign-off line per rule: technique, items exercised out of total, exclusions and who agreed.