diff --git a/api-tests/features/cimit/alternate-doc.feature b/api-tests/features/cimit/alternate-doc.feature index f880578875..bb697d8d5f 100644 --- a/api-tests/features/cimit/alternate-doc.feature +++ b/api-tests/features/cimit/alternate-doc.feature @@ -193,84 +193,6 @@ Feature: CIMIT - Alternate doc | 'drivingLicence' | 'kenneth-driving-permit-needs-alternate-doc' | 'pyi-driving-licence-no-match-another-way' | 'ukPassport' | 'kenneth-passport-valid' | | 'ukPassport' | 'kenneth-passport-needs-alternate-doc' | 'pyi-passport-no-match-another-way' | 'drivingLicence'| 'kenneth-driving-permit-valid' | - Scenario Outline: Alternate doc mitigation via passport or DL - HMRC KBV - Given I activate the 'm2bBetaHmrcKbv' feature set - When I start a new 'medium-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'appTriage' event - Then I get a 'dcmaw' CRI response - When I call the CRI stub and get an 'access_denied' OAuth error - Then I get a 'page-multiple-doc-check' page response - When I submit an event - Then I get a CRI response - When I submit details to the CRI stub - Then I get a page response - When I submit a 'next' event - Then I get a CRI response - When I submit details to the CRI stub that mitigate the 'NEEDS-ALTERNATE-DOC' CI - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P2' identity - - Examples: - | initialCri | initialInvalidDoc | noMatchPage | mitigatingCri | mitigatingDoc | - | 'drivingLicence' | 'kenneth-driving-permit-needs-alternate-doc' | 'pyi-driving-licence-no-match-another-way' | 'ukPassport' | 'kenneth-passport-valid' | - | 'ukPassport' | 'kenneth-passport-needs-alternate-doc' | 'pyi-passport-no-match-another-way' | 'drivingLicence'| 'kenneth-driving-permit-valid' | - - Scenario Outline: Alternate doc mitigation user drops out of HMRC KBV CRI via thin file or failed checks - HMRC KBV - Given I activate the 'm2bBetaHmrcKbv' feature set - When I start a new 'medium-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'appTriage' event - Then I get a 'dcmaw' CRI response - When I call the CRI stub and get an 'access_denied' OAuth error - Then I get a 'page-multiple-doc-check' page response - When I submit an event - Then I get a CRI response - When I submit details to the CRI stub - Then I get a page response - When I submit a 'next' event - Then I get a CRI response - When I submit details to the CRI stub that mitigate the 'NEEDS-ALTERNATE-DOC' CI - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I call the CRI stub with attributes and get an 'invalid_request' OAuth error - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-pre-experian-kbv-transition' page response - When I submit a 'next' event - Then I get a 'kbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P2' identity - - Examples: - | initialCri | initialInvalidDoc | noMatchPage | mitigatingCri | mitigatingDoc | - | 'drivingLicence' | 'kenneth-driving-permit-needs-alternate-doc' | 'pyi-driving-licence-no-match-another-way' | 'ukPassport' | 'kenneth-passport-valid' | - | 'ukPassport' | 'kenneth-passport-needs-alternate-doc' | 'pyi-passport-no-match-another-way' | 'drivingLicence'| 'kenneth-driving-permit-valid' | - Scenario Outline: Mitigation of alternate-doc CI via when user initially drops out of When I submit a '' event Then I get a '' CRI response diff --git a/api-tests/features/disabled-cri-journeys.feature b/api-tests/features/disabled-cri-journeys.feature index aa252946ce..3adffd12ae 100644 --- a/api-tests/features/disabled-cri-journeys.feature +++ b/api-tests/features/disabled-cri-journeys.feature @@ -198,10 +198,10 @@ Feature: Disabled CRI journeys When I submit an 'end' event Then I get a 'pyi-escape' page response - Rule: HMRC and DWP KBVs are disabled + Rule: DWP KBVs are disabled or unsuitable Scenario: Experian KBV is offered first - Given I activate the 'hmrcKbvDisabled,dwpKbvDisabled' feature sets + Given I activate the 'dwpKbvDisabled' feature sets When I start a new 'medium-confidence' journey Then I get a 'page-ipv-identity-document-start' page response When I submit an 'appTriage' event @@ -217,50 +217,6 @@ Feature: Disabled CRI journeys When I submit 'kenneth-score-2' details to the CRI stub Then I get a 'page-pre-experian-kbv-transition' page response - Rule: DWP KBV is disabled and HMRC KBV is enabled - - Scenario: NINO then HMRC KBV is offered if user doesn't have an existing NINO - Given I activate the 'dwpKbvDisabled,hmrcKbvBeta' feature sets - When I start a new 'medium-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'appTriage' event - Then I get a 'dcmaw' CRI response - When I submit an 'access-denied' event - Then I get a 'page-multiple-doc-check' page response - When I submit a 'ukPassport' event - Then I get a 'ukPassport' CRI response - When I submit 'kenneth-passport-valid' details to the CRI stub - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'nino' CRI response - When I submit a 'next' event - Then I get an 'hmrcKbv' CRI response - - Scenario: HMRC KBV is offered if user already has a NINO - Given I activate the 'dwpKbvDisabled,m2bBetaHmrcKbv' feature sets - When I start a new 'medium-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'end' event - Then I get a 'page-ipv-identity-postoffice-start' page response - When I submit an 'end' event - Then I get a 'prove-identity-no-photo-id' page response - When I submit an 'next' event - Then I get a 'claimedIdentity' CRI response - When I submit a 'next' event - Then I get a 'bav' CRI response - When I submit a 'next' event - Then I get a 'nino' CRI response - When I submit a 'next' event - Then I get an 'address' CRI response - When I submit a 'next' event - Then I get a 'fraud' CRI response - When I submit a 'next' event - Then I get a 'hmrcKbv' CRI response - - Rule: HMRC KBV is disabled - Scenario: Experian KBV is offered if DWP KBV unsuitable Given I activate the 'dwpKbvTest' feature set When I start a new 'medium-confidence' journey diff --git a/api-tests/features/p1-journeys.feature b/api-tests/features/p1-journeys.feature index 31bc07611a..846eccf0fe 100644 --- a/api-tests/features/p1-journeys.feature +++ b/api-tests/features/p1-journeys.feature @@ -272,33 +272,6 @@ Feature: P1 journey When I use the OAuth response to get my identity Then I get a 'P1' identity - Scenario: P1 Validate the Evidence requested for low confidence journey in HMRC KBV - Given I activate the 'p1Journeys,m2bBetaHmrcKbv' feature set - When I start a new 'low-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'appTriage' event - Then I get a 'dcmaw' CRI response - When I call the CRI stub and get an 'access_denied' OAuth error - Then I get a 'page-multiple-doc-check' page response with context 'nino' - When I submit an 'ukPassport' event - Then I get a 'ukPassport' CRI response - When I submit 'kenneth-passport-valid' details to the CRI stub - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-1' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-1' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I submit 'kenneth-score-1' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":1} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P1' identity - Scenario: P1 thin file for low confidence users with photo ID Given I activate the 'p1Journeys' feature set When I start a new 'low-confidence' journey diff --git a/api-tests/features/p1-no-photo-id.feature b/api-tests/features/p1-no-photo-id.feature index e880243e5b..d6a3936203 100644 --- a/api-tests/features/p1-no-photo-id.feature +++ b/api-tests/features/p1-no-photo-id.feature @@ -224,70 +224,6 @@ Feature: P1 No Photo Id Journey When I use the OAuth response to get my identity Then I get a 'P1' identity - Scenario: P1 No Photo Id Journey - HMRC KBV - Given I activate the 'p1Journeys,m2bBetaHmrcKbv' feature sets - When I start a new 'low-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'end' event - Then I get a 'prove-identity-no-photo-id' page response with context 'nino' - When I submit an 'next' event - Then I get a 'claimedIdentity' CRI response - When I submit 'kenneth-current' details with attributes to the CRI stub - | Attribute | Values | - | context | "hmrc_check" | - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","strengthScore":2} | - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":1} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P1' identity - - Scenario: P1 No Photo Id Journey user drops out of HMRC KBV CRI via thin file or failed checks - HMRC KBV - Given I activate the 'p1Journeys,m2bBetaHmrcKbv' feature sets - When I start a new 'low-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'end' event - Then I get a 'prove-identity-no-photo-id' page response with context 'nino' - When I submit an 'next' event - Then I get a 'claimedIdentity' CRI response - When I submit 'kenneth-current' details with attributes to the CRI stub - | Attribute | Values | - | context | "hmrc_check" | - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","strengthScore":2} | - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I call the CRI stub with attributes and get an 'access_denied' OAuth error - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":1} | - Then I get a 'page-pre-experian-kbv-transition' page response - When I submit a 'next' event - Then I get a 'kbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":1} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P1' identity - Scenario: P1 No suitable ID Given I activate the 'p1Journeys' feature set When I start a new 'low-confidence' journey diff --git a/api-tests/features/p2-no-photo-id.feature b/api-tests/features/p2-no-photo-id.feature index ff7393b79e..c88e052f1d 100644 --- a/api-tests/features/p2-no-photo-id.feature +++ b/api-tests/features/p2-no-photo-id.feature @@ -151,42 +151,6 @@ Feature: P2 no photo id journey | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | Then I get a 'no-photo-id-security-questions-find-another-way' page response - Rule: HMRC KBV - Background: Start P2 no photo id with HMRC KBV - Given I activate the 'm2bBetaHmrcKbv' feature set - When I start a new 'medium-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'end' event - Then I get a 'page-ipv-identity-postoffice-start' page response - When I submit an 'end' event - Then I get a 'prove-identity-no-photo-id' page response - When I submit an 'next' event - - Scenario: P2 no photo id journey - HMRC - Happy path - Then I get a 'claimedIdentity' CRI response - When I submit 'kenneth-current' details with attributes to the CRI stub - | Attribute | Values | - | context | "bank_account" | - Then I get a 'bav' CRI response - When I submit 'kenneth' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","strengthScore":2} | - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P2' identity - Scenario: P2 no photo id journey - Experian - Breaching BAV CI Then I get a 'claimedIdentity' CRI response When I submit 'kenneth-current' details with attributes to the CRI stub @@ -196,92 +160,6 @@ Feature: P2 no photo id journey When I submit 'kenneth-with-breaching-ci' details to the CRI stub Then I get a 'pyi-no-match' page response with context 'bankAccount' - Scenario: P2 no photo id journey - HMRC - Breaching NINO CI - Then I get a 'claimedIdentity' CRI response - When I submit 'kenneth-current' details with attributes to the CRI stub - | Attribute | Values | - | context | "bank_account" | - Then I get a 'bav' CRI response - When I submit 'kenneth' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-with-breaching-ci' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","strengthScore":2} | - Then I get a 'pyi-no-match' page response with context 'nino' - - Scenario: P2 no photo id journey - HMRC - Drops out via thin file or failed checks - Then I get a 'claimedIdentity' CRI response - When I submit 'kenneth-current' details with attributes to the CRI stub - | Attribute | Values | - | context | "bank_account" | - Then I get a 'bav' CRI response - When I submit 'kenneth' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","strengthScore":2} | - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I call the CRI stub with attributes and get an 'invalid_request' OAuth error - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-pre-experian-kbv-transition' page response - When I submit a 'next' event - Then I get a 'kbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P2' identity - - Scenario: P2 no photo id journey - HMRC - Breaching KBV CI - Then I get a 'claimedIdentity' CRI response - When I submit 'kenneth-current' details with attributes to the CRI stub - | Attribute | Values | - | context | "bank_account" | - Then I get a 'bav' CRI response - When I submit 'kenneth' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","strengthScore":2} | - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I submit 'kenneth-with-breaching-ci' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'pyi-no-match' page response - - Scenario: P2 no photo id journey - HMRC - KBV CI mitigation - Then I get a 'claimedIdentity' CRI response - When I submit 'kenneth-current' details with attributes to the CRI stub - | Attribute | Values | - | context | "bank_account" | - Then I get a 'bav' CRI response - When I submit 'kenneth' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","strengthScore":2} | - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I submit 'kenneth-needs-enhanced-verification' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'no-photo-id-security-questions-find-another-way' page response - Rule: Abandon Background: Abandon P2 no photo id journey Given I activate the 'm2bBetaHmrcKbv' feature set diff --git a/api-tests/features/p2-web-journey.feature b/api-tests/features/p2-web-journey.feature index a8d8d1605c..68d65b3c7d 100644 --- a/api-tests/features/p2-web-journey.feature +++ b/api-tests/features/p2-web-journey.feature @@ -176,110 +176,6 @@ Feature: P2 Web document journey | drivingLicence | kenneth-driving-permit-valid | | ukPassport | kenneth-passport-valid | - Scenario Outline: Successful P2 identity via Web using - HMRC KBV - Given I activate the 'm2bBetaHmrcKbv' feature set - When I start a new 'medium-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'appTriage' event - Then I get a 'dcmaw' CRI response - When I call the CRI stub and get an 'access_denied' OAuth error - Then I get a 'page-multiple-doc-check' page response - When I submit a '' event - Then I get a '' CRI response - When I submit '
' details to the CRI stub - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P2' identity - - Examples: - | cri | details | - | drivingLicence | kenneth-driving-permit-valid | - | ukPassport | kenneth-passport-valid | - - Scenario Outline: User drops out of HMRC KBV CRI via thin file or failed checks using - HMRC KBV - Given I activate the 'm2bBetaHmrcKbv' feature set - When I start a new 'medium-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'appTriage' event - Then I get a 'dcmaw' CRI response - When I call the CRI stub and get an 'access_denied' OAuth error - Then I get a 'page-multiple-doc-check' page response - When I submit a '' event - Then I get a '' CRI response - When I submit '
' details to the CRI stub - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'hmrcKbv' CRI response - When I call the CRI stub with attributes and get an 'access_denied' OAuth error - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-pre-experian-kbv-transition' page response - When I submit a 'next' event - Then I get a 'kbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P2' identity - - Examples: - | cri | details | - | drivingLicence | kenneth-driving-permit-valid | - | ukPassport | kenneth-passport-valid | - - Scenario Outline: User drops out of NINO CRI after - HMRC KBV - Given I activate the 'm2bBetaHmrcKbv' feature set - When I start a new 'medium-confidence' journey - Then I get a 'page-ipv-identity-document-start' page response - When I submit an 'appTriage' event - Then I get a 'dcmaw' CRI response - When I call the CRI stub and get an 'access_denied' OAuth error - Then I get a 'page-multiple-doc-check' page response - When I submit a '' event - Then I get a '' CRI response - When I submit '
' details to the CRI stub - Then I get an 'address' CRI response - When I submit 'kenneth-current' details to the CRI stub - Then I get a 'fraud' CRI response - When I submit 'kenneth-score-2' details to the CRI stub - Then I get a 'nino' CRI response - When I submit 'kenneth-score-0' details to the CRI stub - Then I get a 'page-pre-experian-kbv-transition' page response - When I submit a 'next' event - Then I get a 'kbv' CRI response - When I submit 'kenneth-score-2' details with attributes to the CRI stub - | Attribute | Values | - | evidence_requested | {"scoringPolicy":"gpg45","verificationScore":2} | - Then I get a 'page-ipv-success' page response - When I submit a 'next' event - Then I get an OAuth response - When I use the OAuth response to get my identity - Then I get a 'P2' identity - - Examples: - | cri | details | - | drivingLicence | kenneth-driving-permit-valid | - | ukPassport | kenneth-passport-valid | - Scenario Outline: Allows use of when user drops out of CRI When I submit a '' event Then I get a '' CRI response