Calling a service by hand
Sending a request to an OData service or a push channel on an ABAP system and reading what comes back, while building it or chasing an error, before any client exists. Distinct from unit testingUnit testingTesting application logic without a running business process — and the test doubles that make dependencies on the database and on framework services tractable.SAP and community, unassessed, which proves logic in code and keeps the proof.
Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP
Overview
The service binding editor in ADT carries a Service URL link. Opened in a browser it shows the service document, and adding /$metadata to it shows the metadata — the one way ADT lets a developer call a RAP OData service before a client exists.
Not covered: That link only sends a GET, to the service document or its metadata: no method to choose, no header to add, no payload to send. ABAP Cloud systems carry no SAP GUI, so SAP Gateway Client, Standard ABAP's request builder, is not available there.
This assesses OData testing only; ABAP Push Channels in ABAP Cloud were not checked.
No community artifact is documented here.
Artifacts
Nothing is mapped here yet.
Details
Coverage
For your agent
- Ref
capability:abap-service-testing- JSON
- /capabilities/abap-service-testing.json
- MCP
- Connecting an agent