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

Lesson 5 of 6

End-to-end tests across SAP BTP and SAP S/4HANA

9 min

Listen to this lesson

0:00 / 15:46

End-to-end tests prove that the business process works across both platforms with real configuration: identity, destinations, Cloud Connector, event broker, role collections and SAP S/4HANA data. They are expensive, so Contoso keeps a short list, chosen with Dan and Maria as the scenarios the business would notice first if they broke.

ScenarioSystems touchedPass criteria
E2E-01 Fleet desk sees order statusIdentity, app, destination, Cloud Connector, CMQ Sales Order APIStatus in the app matches the order in CMQ for Great Lakes Fleet Services
E2E-02 Order change raises an inquiry updateCMQ, event channel, broker, appMaria changes the requested delivery date in CMQ; the app's inquiry shows the change within the agreed time
E2E-03 Supervisor closes an inquiryApp, authorization, databaseClosed with resolution; agent cannot close; audit fields correct
E2E-04 Supervisor action written to SAP S/4HANAApp, principal propagation, Cloud Connector, CMQChange appears in CMQ under the supervisor's own user
E2E-05 Fleet customer sees only own dataIdentity attributes, appGreat Lakes Fleet Services contact sees only their inquiries
E2E-06 Same event delivered twiceBroker, appOne inquiry update, no duplicate

Contoso's end-to-end scenarios for the fleet app's first release.

Where Contoso's end-to-end scenarios run: each one crosses a different set of systems, so together they cover every link in the landscape.
The Sign-Off Table · thesignofftable.com/academy/sap-btp-301

Make the landscape ready first

Test data in CMQ client 100Sales orders for the Great Lakes Fleet Services test customer with CMC-ALT-100, sales area 1710 / 10 / 00, plant 1710; some delivered, some open, one blocked
SAP S/4HANA configurationAPIs active; event channel and outbound binding for sales order events; certificate mapping for propagation
ConnectivityCloud Connector connected to cmc-ext-test; mappings and paths exposed; destinations point to CMQ client 100
Identity and rolesTest identities per role in the right groups; role collections mapped in cmc-ext-test
AppThe release candidate deployed by transport; version recorded
The readiness checklist Contoso runs before end-to-end testing.
The Sign-Off Table · thesignofftable.com/academy/sap-btp-301

A readiness check takes an hour and saves days. Each layer gets one quick proof: a smoke call per destination, a test event published and seen in the broker, a sign-in per test identity, and a look at the prepared orders in CMQ. Only when all are green does the end-to-end cycle start, so failures during the cycle point to the process, not the plumbing.

Asynchronous steps and timing

Event-driven steps, such as E2E-02, are asynchronous: the change is saved in CMQ before the app has received and processed the event. Tests must wait for a condition, not a fixed time: poll the app's inquiry until the new date appears, with a time-out based on the agreed service level, and record how long it took. A fixed wait is either too short (random failures) or too long (slow suites). When the time-out passes, the evidence should show where the event stopped: in CMQ, in the broker queue, or in the app.

An asynchronous step waits for a condition with a time-out, and records how long the event really took.
The Sign-Off Table · thesignofftable.com/academy/sap-btp-301
  1. Act in SAP S/4HANAMaria changes the requested delivery date of a test fleet order in CMQ
  2. Event publishedThe sales order changed event leaves CMQ through the channel
  3. BrokerDelivered to the fleet app's queue
  4. App processesReads the order through the API and updates the inquiry
  5. Poll until trueThe test checks the inquiry until the new date appears or the time-out passes
  6. RecordResult, elapsed time and, on failure, where the event stopped
E2E-02 step by step, with a condition-based wait.
The Sign-Off Table · thesignofftable.com/academy/sap-btp-301

If an app is multitenant, end-to-end testing adds a dimension: run the key scenarios in at least two subscriber tenants and prove that data, users and configuration do not leak between them. The fleet app is single-tenant, so Contoso skips this, but its approach to proving data separation between fleet customers (E2E-05) follows the same idea.

What would you do?

E2E-02 passes on some runs and fails on others. The test waits 10 seconds after Maria's change and then checks the inquiry. Logs show the event sometimes takes 14 seconds to be processed. What should the test team change?

Key points
  • Keep a short list of end-to-end scenarios chosen with process owners and key users.
  • Run a readiness check of data, SAP S/4HANA configuration, connectivity, identity and app version first.
  • Wait for conditions, not fixed times, in asynchronous steps; record the elapsed time.
  • For multitenant apps, prove isolation across at least two subscriber tenants.
  • Record scenarios, evidence and sign-off in SAP Cloud ALM.

Check your understanding · not graded

Lesson check

  1. 1. Why run a readiness check before an end-to-end cycle?

  2. 2. How should a test wait for an event-driven update?

  3. 3. Which evidence proves scenario E2E-04 (supervisor action written to SAP S/4HANA)?

  4. 4. What does a multitenant app add to end-to-end testing?