3788542 - API automated test scripts get stuck when binding TDC data in Test Automation Tool

• API test gets stuck when using TDC as a data source, no progress is made the UI shows stuck at 0%.
• The same API test without TDC are progressing successfully.

SAP S/4HANA Cloud Public Edition

1. Run an API test without binding any TDC data and verify it completes successfully within a short time.
2. Run the same API test with TDC data bound and observe that the execution remains in progress and does not complete while the SOAP error log shows no errors.

TDC binding is supported only for ODATA APIs. When attempting to bind TDC data for a SOAP API, the test does not progress.

Determine the API protocol used by the test (OData or SOAP).

If the API is SOAP, do not use TDC binding; instead, provide the input data directly in the payload or maintain values manually for each field.

If TDC binding is required, switch to an equivalent OData API (where available) and bind TDC data either for the entire payload or by mapping values per field using the value help.

This can be confirmed in the FAQ section of the Test Automation Tool page 

"Is it possible to bind TDC (test data container) data with API automates?

TDC binding is supported only for ODATA APIs. Binding with TDC can be done in two ways: you can either bind the whole payload structure with TDC data using the Bind TDC Data feature; or you can map TDC data in the payload itself using the value help provided for each input field."

refer to: Test Automation Tool FAQ: TDC binding limitations

tdc binding, odata api, soap api, test automation tool, api test stuck, execution in progress, no errors in soap log, test data container, api payload, binding limitation, s/4hana cloud , KBA , CA-CTT-S4C-API , Test Automation Tool Component for API tests , Problem