Skip to content

Update click-to-dial feature files with resource URLs and x-correlator #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
YadingFang merged 2 commits into from
Feb 10, 2026
Merged

Update click-to-dial feature files with resource URLs and x-correlator #66

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2303ded
test: update click-to-dial feature files with resource URLs and x-cor…
YadingFang Feb 6, 2026
6a4fed8
tests: reference XCorrelator schema in .feature backgrounds
Feb 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions code/Test_definitions/click-to-dial-createCall.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,13 @@ Feature: CAMARA Click to Dial API, vwip - Operation createCall
# References to OAS spec schemas refer to schemas specified in click-to-dial.yaml

Background: Common createCall setup
Given an environment at "apiRoot" |
Given an environment at "apiRoot"
And the resource "/click-to-dial/v0.1rc1/calls"
And the header "Content-Type" is set to "application/json"
And the header "Authorization" is set to a valid access token
# Properties not explicitly overwritten in the Scenarios can take any values compliant with the schema
And the header "x-correlator" is set to a valid UUID
And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"
# Properties not explicitly overwritten in the Scenarios can take any values compliant with the schema
And the request body is set by default to a request body compliant with the schema at "/components/schemas/CreateCallRequest"

# Success scenarios
Expand Down
7 changes: 5 additions & 2 deletions code/Test_definitions/click-to-dial-getRecording.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,13 @@ Feature: CAMARA Click to Dial API, vwip - Operation getRecording
# References to OAS spec schemas refer to schemas specified in click-to-dial.yaml

Background: Common getRecording setup
Given an environment at "apiRoot" |
Given an environment at "apiRoot"
And the resource "/click-to-dial/v0.1rc1/calls/{callId}/recording"
And the header "Content-Type" is set to "application/json"
And the header "Authorization" is set to a valid access token
# Path parameters not explicitly overwritten in the Scenarios can take any values compliant with the schema
And the header "x-correlator" is set to a valid UUID
And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"
# Path parameters not explicitly overwritten in the Scenarios can take any values compliant with the schema

# Success scenarios
@getrecording_success
Expand Down
7 changes: 5 additions & 2 deletions code/Test_definitions/click-to-dial-terminateCall.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,13 @@ Feature: CAMARA Click to Dial API, vwip - Operation terminateCall
# References to OAS spec schemas refer to schemas specified in click-to-dial.yaml

Background: Common terminateCall setup
Given an environment at "apiRoot" |
Given an environment at "apiRoot"
And the resource "/click-to-dial/v0.1rc1/calls/{callId}"
And the header "Content-Type" is set to "application/json"
And the header "Authorization" is set to a valid access token
# Path parameters not explicitly overwritten in the Scenarios can take any values compliant with the schema
And the header "x-correlator" is set to a valid UUID
And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"
# Path parameters not explicitly overwritten in the Scenarios can take any values compliant with the schema

# Success scenarios
@terminatecall_success
Expand Down
Loading