API and Service Test Automation for OData, SOAP and IDoc

Keep this: job aid

Service test automation cheat sheet

• OData: check $metadata first; filter to your own data with $filter and $select; page with $top/$skip.
• OData writes: GET with X-CSRF-Token: Fetch, keep the cookies, send the token on POST/PATCH/DELETE; 403 means token or session problem.
• Updates: send If-Match with the ETag; test that a stale ETag is rejected (412).
• $batch: change sets are atomic; prove no partial postings remain after a failure.
• SOAP: generate requests from the WSDL, validate responses against the schema, keep endpoints in configuration (SOAMANAGER, destinations).
• SOAP results: Sender fault = bad message, Receiver fault = processing failure; business errors may sit in a valid response.
• IDoc: 64 ready, 53 posted, 51 not posted; send through the real channel; read status records on failure.
• Always finish with a business assertion on the posted document, never just a status code.
• Data factories: fresh, minimal, unique run reference; clean up by reject, block, reverse or cancel.
• Diagnose with /IWFND/GW_CLIENT, /IWFND/ERROR_LOG and BD87; record request, response and document numbers as evidence.