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.
Overview
SAP Gateway Client (/IWFND/GW_CLIENT) sends HTTP requests to an OData service with a chosen method, URI options, headers and payload, and saves test cases to replay.
The page checked covers OData only; ABAP Push Channels are not mentioned in it, and how the community tools relate to the Gateway Client has not been assessed.
An installable request builder that also connects to ABAP Push Channels, ODAPUODAPUA UI5 app installed with abapGit that builds and saves test requests for OData services and connects to ABAP Push Channels, on S/4HANA systems.independent, abap, and an ABAP client library that sends OData calls and chains assertions on the response, abap-odata-testabap-odata-testAn ABAP client library for calling OData services and chaining assertions on the response, such as assert_http_200, for unit tests, ADT console runs and standalone programs; its examples show GET only.independent, abap.
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:abap-service-testing- JSON
- /capabilities/abap-service-testing.json
- MCP
- Connecting an agent