[Masa8106]

What type of PR is this?

• correction

What this PR does / why we need it:

To Align number recycling with Commonalities r4.4 in terms of testing

Which issue(s) this PR fixes:

Fixes #126

Special notes for reviewers:

Updates are based on the following three points:

• Using operationId in request sending description
• Aligning with sample-service-template.feature
• Aligning with C02-phoneNumber-errors.feature

Changelog input

 release-note
  -To Align number recycling with Commonalities r4.4 in terms of testing

Additional documentation

None

[Masa8106]

@eric-murray, @grgpapadopoulos, would you review this PR?

[albertoramosmonagas]

This is a Scenario, not a Scenario Outline, and has no Examples, so <invalid_specifiedDate> is never substituted. Either use a literal invalid value or convert it to an Outline with Examples.

[Masa8106]

Thank you for pointing out. I have updated it with literal explanation.

[albertoramosmonagas]

Template scenarios that apply are missing: 400.05_missing_required_property (specifiedDate is required) and 400.06_invalid_x-correlator. In the template, 400.04 and 400.05 are different scenarios (empty_property, missing_required_property). The PR reuses those numbers for its own cases (out_of_range, invalid_specifiedDate). Please renumber the custom cases after the generic ones, or give them a different convention.

[Masa8106]

@albertoramosmonagas, thank for pointing out. I have tried to resolve it. Please check it.

[albertoramosmonagas]

LGTM with te new changes