Skip to content

Possible incorrect test definitions for @KYC_Match_5_success_specific_property_false #57

@minpatelgsma

Description

@minpatelgsma

Problem description

I believe that Test definitions for KYC_Match_5_success_specific_property_false is incorrect . Description of test below is incorrect. Please can you confirm.
This is the Current Test step definition set to:
` @KYC_Match_5_success_specific_property_false

This scenario test the false result as scenario KYC_Match_3_success_specific_property_score but without the score properties

Scenario Outline: Validate success response when providing specific property with false value and without the score properties
Given a valid testing phone number supported by the service, identified by the access token or provided in the request body
And the request body is set to a valid parameter combination with property "<request_property_path>" set to a valid formatted value that does perfectly match the value stored in the MNO system
When the request "KYC_Match" is sent
Then the response status code is 200
And the response header "x-correlator" has same value as the request header "x-correlator"
And the response header "Content-Type" is "application/json"
And the response body complies with the OAS schema at "/components/schemas/KYC_MatchResponse"
And the response property "<response_property_path>" is equal to "false"`

As you can see Scenario title says: Validate success response when providing specific property with false value and without the score properties however requirement says set to a valid formatted value that **does perfectly match** the value stored in the MNO system

should the requirement actually does NOT match ?

Expected behaviour

  1. Please confirm above test definition is incorrect.
  2. Test definition to be updated if it is incorrect.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions