Skip to content

Fix Centralized Linter Tests issues #56

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
PedroDiez merged 1 commit into from
Aug 21, 2025
Merged

Fix Centralized Linter Tests issues #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
34 changes: 17 additions & 17 deletions code/Test_definitions/customer-insights-retrieveScoring.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,11 +239,11 @@ Feature: CAMARA Customer Insights API, v0.2.0-rc.1 - Operation retrieveScoring
And the response property "$.status" is 422
And the response property "$.code" is "CUSTOMER_INSIGHTS.ID_DOCUMENT_NOT_SUPPORTED"
And the response property "$.message" contains a user friendly text

Examples:
| score_type |
| gaugeMetric |
| veritasIndex |
| score_type |
| gaugeMetric |
| veritasIndex |

@retrieve_scoring_422.06_id_document_not_supported_two_legged_with_scoring_type
Scenario Outline: Id Document not supported with 2-legged token and scoringType
Expand All @@ -256,12 +256,12 @@ Feature: CAMARA Customer Insights API, v0.2.0-rc.1 - Operation retrieveScoring
And the response property "$.status" is 422
And the response property "$.code" is "CUSTOMER_INSIGHTS.ID_DOCUMENT_NOT_SUPPORTED"
And the response property "$.message" contains a user friendly text

Examples:
| score_type |
| gaugeMetric |
| veritasIndex |
| score_type |
| gaugeMetric |
| veritasIndex |

@retrieve_scoring_422.07_id_document_required_three_legged
Scenario: Id Document required with 3-legged token
Given the header "Authorization" is set to a valid access token identifying a phone number
Expand Down Expand Up @@ -298,11 +298,11 @@ Feature: CAMARA Customer Insights API, v0.2.0-rc.1 - Operation retrieveScoring
And the response property "$.status" is 422
And the response property "$.code" is "CUSTOMER_INSIGHTS.ID_DOCUMENT_REQUIRED"
And the response property "$.message" contains a user friendly text

Examples:
| score_type |
| gaugeMetric |
| veritasIndex |
| score_type |
| gaugeMetric |
| veritasIndex |

@retrieve_scoring_422.10_id_document_required_two_legged_with_scoring_type
Scenario Outline: Id Document required with 2-legged token and scoringType
Expand All @@ -316,11 +316,11 @@ Feature: CAMARA Customer Insights API, v0.2.0-rc.1 - Operation retrieveScoring
And the response property "$.status" is 422
And the response property "$.code" is "CUSTOMER_INSIGHTS.ID_DOCUMENT_REQUIRED"
And the response property "$.message" contains a user friendly text

Examples:
| score_type |
| gaugeMetric |
| veritasIndex |
| score_type |
| gaugeMetric |
| veritasIndex |

@retrieve_scoring_C02.03_unnecessary_phone_number
Scenario: Phone number not to be included when it can be deduced from the access token
Expand Down