Architecting for Testability and Quality

Keep this: job aid

Testability design review card

• Controllability: APIs to create and reset data; configurable dates and parameters.
• Observability: application log entries with message IDs and business keys, on success and failure.
• Isolation: business rules in classes callable by ABAP Unit; stable, developer-set UI IDs.
• Correlation key on every hop; business context exposed for Cloud ALM message search.
• Monitoring checks outcomes, not just completion; set it up in test systems first.
• Each environment: purpose, data strategy, refresh rule; masking verified after every refresh.
• Synthetic data in versioned code; owned stubs for unavailable partners.
• Contracts: structure, meaning, errors, versioning; consumer checks run by the provider.
• Toggles: reuse configuration, check reversibility, test on and off, owner and removal date.
• Evidence: requirement → test → run → defect → transport → production, linked in SAP Cloud ALM.