Missing Gherkin test definition for getCall operation

[hdamker]

Problem description
code/API_definitions/click-to-dial.yaml defines the getCall operation on GET /calls/{callId}, but code/Test_definitions/ currently contains feature files only for:

• createCall
• terminateCall
• getRecording

There is no dedicated Gherkin test definition for getCall, so the API definition and test definitions are not fully aligned.

Expected action
Add a test definition file for the getCall operation, for example:

code/Test_definitions/click-to-dial-getCall.feature

It should cover at least:

• successful retrieval of call details (200)
• invalid request / missing path input handling as applicable (400)
• authentication failure (401)
• authorization failure (403) if supported by the API behavior
• unknown call identifier (404)

The scenarios should align with the Call response schema and the declared error responses in click-to-dial.yaml.

Additional context
Relevant files:

• code/API_definitions/click-to-dial.yaml
• code/Test_definitions/click-to-dial-createCall.feature
• code/Test_definitions/click-to-dial-terminateCall.feature
• code/Test_definitions/click-to-dial-getRecording.feature

The missing operation is:

• GET /calls/{callId}
• operationId: getCall