Skip to content

fix: align test feature files with API definition operationIds - #148

Merged
tlohmar merged 3 commits into
camaraproject:mainfrom
jimfengjinhua:fix/test-operationid-alignment
Aug 10, 2026
Merged

fix: align test feature files with API definition operationIds#148
tlohmar merged 3 commits into
camaraproject:mainfrom
jimfengjinhua:fix/test-operationid-alignment

Conversation

@jimfengjinhua

@jimfengjinhua jimfengjinhua commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

What type of PR is this?

Add one of the following kinds:

  • correction
  • tests

What this PR does / why we need it:

Fixes for issue #138 and #143

dedicated-network-accesses.feature — operationId alignment (6 mismatches):

  • listNetworkAccesseslistAccesses (tags + When steps)
  • createNetworkAccesscreateAccess (tags + When steps)
  • readNetworkAccessreadAccess (tags + When steps)
  • deleteNetworkAccessdeleteAccess (tags + When steps)
  • addDevicesRequestaddDevicesToAccess (When steps)
  • removeDevicesRequestremoveDevicesFromAccess (When steps)

dedicated-network-areas.feature — operationId alignment (2 mismatches):

  • retrieveServiceAreasretrieveNetworkServiceAreas (When steps)
  • readServiceAreareadNetworkServiceArea (When steps)

dedicated-network-areas.feature — duplicate numbering:

  • Second _06_ scenario renumbered to _07_; error scenarios renumbered accordingly (_08_, etc.)

dedicated-network-areas.feature — incorrect tag prefix:

  • @areas_retrieveServiceAreas_04_...@dedicated_network_areas_retrieveNetworkServiceAreas_08_...
  • @areas_readServiceArea_02_...@dedicated_network_areas_readNetworkServiceArea_02_...
  • @areas_readServiceArea_03_...@dedicated_network_areas_readNetworkServiceArea_03_...
Additional fixes found during review

dedicated-network-accesses.feature:

  • Tag addDeviceAccessaddDevicesToAccess (tag didn't mirror operationId)
  • Tag removeNetworkaccessremoveDevicesFromAccess (tag didn't mirror operationId)
  • Schema reference CreateNetworkAccessCreateAccessRequest (non-existent schema)
  • Added new listDevices scenario (operationId existed in API but had no test coverage)

dedicated-network-areas.feature:

  • Tags retrieveServiceAreasretrieveNetworkServiceAreas (full operationId alignment in tags, not just When steps)
  • Tags readServiceAreasreadNetworkServiceArea (plural→singular + full operationId)
  • Added x-correlator response header assertions to all scenarios (including error scenarios)
  • Added $.code assertions to error scenarios
  • Changed invalid-UUID scenario expected status from 404 to 400 (semantically correct for malformed input)

Which issue(s) this PR fixes:

Fixes #138 #143

Special notes for reviewers:

This PR includes a few extra changes for some issues that were not mentioned in the original issue #138 and #143.

Changelog input

 release-note

Additional documentation

docs

Fixes camaraproject#143: corrects operationId mismatches in When steps and scenario
tags for dedicated-network-accesses.feature and dedicated-network-areas.feature,
fixes duplicate _06_ numbering, fixes schema reference to CreateAccessRequest,
and adds missing x-correlator assertions and listDevices scenario.
Comment thread code/Test_definitions/dedicated-network-areas.feature Outdated
tlohmar
tlohmar previously approved these changes Aug 10, 2026

@tlohmar tlohmar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@tlohmar tlohmar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks much better. Thx

@tlohmar
tlohmar merged commit a5cedbc into camaraproject:main Aug 10, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Accesses API] Test definition: Missing scenario for GET /accesses/{accessId}/devices (listDevices)

2 participants