diff --git a/features/proof/sendOutOfBandPresentationRequest.feature b/features/proof/sendOutOfBandPresentationRequest.feature index 71b716efd962bc4ab03b95cabc238938aa576bae..0eb05fd18bea38dcdbf5ca2c3a5a06fe32b8e5d8 100644 --- a/features/proof/sendOutOfBandPresentationRequest.feature +++ b/features/proof/sendOutOfBandPresentationRequest.feature @@ -1,38 +1,59 @@ -Feature: Send Out Of Band Presentation Request - I want to verify user credentials. - -Scenario: Send Out Of Band Presentation Request - Given I have passed all the required proof presentation details. - When I have passed all invalid proof presentation details. - Then should return the presentation request required following attributes ( attributes, schemaId or credentialDefId ). - -Scenario: Send Out Of Band Presentation Request - Given I have passed credential_def_id. - When I pass invalid credential_def_id. - Then should return the 400 status code. - -Scenario: Send Out Of Band Presentation Request - Given I have passed attributes. - When I pass invalid attributes. - Then should return the 400 status code. - -Scenario: Send Out Of Band Presentation Request - Given I have passed attributes and credential_def_id. - When I pass valid attributes. - And I pass valid credential_def_id. - Then should return the 400 status code. - -Scenario: Send Out Of Band Presentation Request - Given I have passed attributes and credential_def_id. - When I pass valid attributes. - And I pass invalid credential_def_id. - Then should return the 400 status code. - -Scenario: Send Out Of Band Presentation Request0 - Given I have passed all the required proof presentation credential_def_id and attributes. - When I have passed all valid proof presentation details i.e credential_def_id and attributes. - Then the proof presentation request sent to the holder with provided attributes. - And should return presentation id - And store presentation id, status, their_did into OCM database. - And should return the valid status code 201. +As a OCM Admin + I want to verify credentials without connection. + +Scenario: OCM admin verify credentials + Given PCM user should hold credentials in there wallet. + When OCM verifer orgnization sends a proof presentation request with following fields ( schemaId or credentialDefId, attributes ) to PCM user. + And PCM user share the attributes from requested credentials to OCM verifer. + And OCM verifer verify the presentation acknowledgement. + Then Presentation request should be in 'verified' state. + +Scenario: OCM admin verify credentials + Given PCM user should hold credentials in there wallet. + When OCM admin send a credential request to PCM user. + And PCM user decline the credential request witch will requested from OCM admin. + +Scenario: OCM admin verify credentials + Given PCM user should hold credentials in there wallet. + When OCM admin have not passed all required parameters to proof request. + Then should return the presentation request required following fields ( chemaId or credentialDefId, attributes ). + + +# Feature: Send Out Of Band Presentation Request +# I want to verify user credentials. + +# Scenario: Send Out Of Band Presentation Request +# Given I have passed all the required proof presentation details. +# When I have passed all invalid proof presentation details. +# Then should return the presentation request required following attributes ( attributes, schemaId or credentialDefId ). + +# Scenario: Send Out Of Band Presentation Request +# Given I have passed credential_def_id. +# When I pass invalid credential_def_id. +# Then should return the 400 status code. + +# Scenario: Send Out Of Band Presentation Request +# Given I have passed attributes. +# When I pass invalid attributes. +# Then should return the 400 status code. + +# Scenario: Send Out Of Band Presentation Request +# Given I have passed attributes and credential_def_id. +# When I pass valid attributes. +# And I pass valid credential_def_id. +# Then should return the 400 status code. + +# Scenario: Send Out Of Band Presentation Request +# Given I have passed attributes and credential_def_id. +# When I pass valid attributes. +# And I pass invalid credential_def_id. +# Then should return the 400 status code. + +# Scenario: Send Out Of Band Presentation Request0 +# Given I have passed all the required proof presentation credential_def_id and attributes. +# When I have passed all valid proof presentation details i.e credential_def_id and attributes. +# Then the proof presentation request sent to the holder with provided attributes. +# And should return presentation id +# And store presentation id, status, their_did into OCM database. +# And should return the valid status code 201. diff --git a/features/proof/sendPresentationRequest.feature b/features/proof/sendPresentationRequest.feature index ec82b45b85881dc40f4ec22c0d6bce07d6791135..0380d9c8fb32c30292360ccd827710016dbf705c 100644 --- a/features/proof/sendPresentationRequest.feature +++ b/features/proof/sendPresentationRequest.feature @@ -1,45 +1,52 @@ -Feature: Send Presentation Request - I want to verify user credentials. - -Scenario: Send Presentation Request - Given I have passed all the required proof presentation details. - When I have passed all invalid proof presentation details. - Then should return the presentation request required following attributes ( connectionId, attributes, schemaId or credentialDefId ). - -Scenario: Send Presentation Request - Given I have passed credential_def_id. - When I pass invalid credential_def_id. - Then should return the 400 status code. - -Scenario: Send Presentation Request - Given I have passed connectionId. - When I pass invalid connectionId. - Then should return the 400 status code. - -Scenario: Send Presentation Request - Given I have passed attributes. - When I pass invalid attributes. - Then should return the 400 status code. - -Scenario: Send Presentation Request - Given I have passed connectionId, attributes and credential_def_id. - When I pass valid attributes. - And I pass valid credential_def_id. - And I pass invalid connectionId. - Then should return the 400 status code. - -Scenario: Send Presentation Request - Given I have passed connectionId, attributes and credential_def_id. - When I pass valid attributes. - And I pass invalid credential_def_id. - And I pass valid connectionId. - Then should return the 400 status code. - -Scenario: Send Presentation Request - Given I have passed all the required proof presentation credential_def_id, connectionId and attributes. - When I have passed all valid proof presentation details i.e credential_def_id, connectionId and attributes. - Then the proof presentation request sent to the holder with provided attributes. - And should return presentation id - And store presentation id, status, their_did into OCM database. - And should return the valid status code 201. +As a OCM Admin + I want to verify credentials. + +Scenario: OCM admin verify credentials + Given PCM user should hold credentials in there wallet. + And PCM user connection must be in trusted state with verifer. + When OCM verifer orgnization sends a proof presentation request with following fields ( connectionId, schemaId or credentialDefId, attributes ) to PCM user. + And PCM user share the attributes from requested credentials to OCM verifer. + And OCM verifer verify the presentation acknowledgement. + Then Presentation request should be in 'verified' state. + +Scenario: OCM admin verify credentials + Given PCM user should hold credentials in there wallet. + When OCM admin send a credential request to PCM user. + And PCM user decline the credential request witch will requested from OCM admin. + +Scenario: OCM admin verify credentials + Given PCM user should hold credentials in there wallet. + When OCM admin have not passed all required parameters to proof request. + Then should return the presentation request required following fields ( connectionId, attributes, schemaId or credentialDefId ). + +# Scenario: Send Presentation Request +# Given I have passed credential_def_id. +# When I pass invalid credential_def_id. +# Then should return the 400 status code. + +# Scenario: Send Presentation Request +# Given I have passed connectionId. +# When I pass invalid connectionId. +# Then should return the 400 status code. + +# Scenario: Send Presentation Request +# Given I have passed attributes. +# When I pass invalid attributes. +# Then should return the 400 status code. + +# Scenario: Send Presentation Request +# Given I have passed connectionId, attributes and credential_def_id. +# When I pass valid attributes. +# And I pass valid credential_def_id. +# And I pass invalid connectionId. +# Then should return the 400 status code. + +# Scenario: Send Presentation Request +# Given I have passed connectionId, attributes and credential_def_id. +# When I pass valid attributes. +# And I pass invalid credential_def_id. +# And I pass valid connectionId. +# Then should return the 400 status code. + + diff --git a/features/proof/sendPrincipalCredentialPresentationRequest.feature b/features/proof/sendPrincipalCredentialPresentationRequest.feature index e12676cb8cfec958a273a65b6797d17799a75e04..7c79dae9a179c8f5c3a5290565655be86c3ba75e 100644 --- a/features/proof/sendPrincipalCredentialPresentationRequest.feature +++ b/features/proof/sendPrincipalCredentialPresentationRequest.feature @@ -1,38 +1,35 @@ -Feature: Send Principal Credential Presentation Request - I want to change connection status in trusted state from active state. - So I am able to issue credential to the PCM user. - -Scenario: Send principal credential presentation request - Given I pass valid connection id. - Then the proof presentation request is sent to the holder with provided attributes. +Feature: I am able to issue credential to the PCM user. + To make subscription service connection trusted of an organization. Scenario: Send principal credential presentation request - Given invalid connection id is passed. - Then should return the 500 execption. + Given PCM user should hold credentials in there wallet. + And PCM user connection must be in complete state with verifer. + When OCM verifer orgnization sends a proof presentation request with following fields ( schemaId, attributes ) to PCM user. + And PCM user share the attributes from requested credentials to OCM verifer. + And OCM verifer verify the presentation acknowledgement. + Then Presentation request should be in 'trusted' state. + And PCM user get the principal credential. -Scenario: Send principal credential presentation request - Given I am not passing a connection id. - Then should return the Required following attributes ( presentation_id ) with status code 400. +# Scenario: Send principal credential presentation request +# Given invalid connection id is passed. +# Then should return the 404 execption. -Scenario: Send principal credential presentation request - Given I have passed a connection id and credential type. - When passed connection id is valid. - And passed credential type is valid. - Then the get principal credentials details from the attestation service. - And the proof presentation request sent to the holder with provided attributes. +# Scenario: Send principal credential presentation request +# Given I am not passing a connection id. +# Then should return the Required following attributes ( presentation_id ) with status code 400. -Scenario: Send principal credential presentation request - Given I have passed a connection id and credential type. - When passed connection id is valid. - And passed credential type is invalid. - Then should not received principal credentials details from the attestation service. - And should return the 500 execption. +# Scenario: Send principal credential presentation request +# Given I have passed a connection id and credential type. +# When passed connection id is valid. +# And passed credential type is valid. +# Then the get principal credentials details from the attestation service. +# And the proof presentation request sent to the holder with provided attributes. + +# Scenario: Send principal credential presentation request +# Given I have passed a connection id and credential type. +# When passed connection id is valid. +# And passed credential type is invalid. +# Then should not received principal credentials details from the attestation service. +# And should return the 404 execption. -Scenario: Send principal credential presentation request - Given I have passed all the required proof presentation details. - When I passed valid proof presentation details. - Then the proof presentation request sent to the holder with provided attributes. - And should return presentation id - And store presentation id, status, their_did into OCM database. - And should return the valid status code 201. diff --git a/features/proof/webhookCallForUpdateStatus.feature b/features/proof/webhookCallForUpdateStatus.feature deleted file mode 100644 index 6bf3881be01dfddf91c8751939fe16a2690be0f1..0000000000000000000000000000000000000000 --- a/features/proof/webhookCallForUpdateStatus.feature +++ /dev/null @@ -1,22 +0,0 @@ -Feature: Webhook call for update presentation status. - -Scenario: Received validated DTO from NATS call. - Given Webhook valid object . - When passed presentation status as presentation received. - And passed valid proof request id. - Then should update presentation proof status in DB. - -Scenario: Received validated DTO from NATS call . - Given Webhook valid object . - When passed presentation status as Done. - And passed valid proof request id. - Then should update presentation proof status in DB. - And make connection status to trusted. - -Scenario: Received validated DTO from NATS call And Auto accept request is true. - Given Webhook valid object . - When passed presentation status as presentation received. - And passed valid proof request id. - Then should update presentation proof status in DB. - And accept presentation proof request. - And return valis message "Presentation received request accepted successfully". \ No newline at end of file