-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
test: add anoncreds issuance happy path bdd scenario (#767)
Signed-off-by: Anton Baliasnikov <[email protected]>
- Loading branch information
Anton Baliasnikov
authored
Oct 25, 2023
1 parent
43083a3
commit 5558a9e
Showing
10 changed files
with
171 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
17 changes: 17 additions & 0 deletions
17
tests/integration-tests/src/main/kotlin/models/AnoncredsSchema.kt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
package models | ||
|
||
import com.google.gson.annotations.SerializedName | ||
|
||
class AnoncredsSchema( | ||
@SerializedName("name") | ||
val name: String, | ||
|
||
@SerializedName("version") | ||
val version: String, | ||
|
||
@SerializedName("issuerId") | ||
val issuerId: String, | ||
|
||
@SerializedName("attrNames") | ||
val attrNames: List<String> | ||
) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
23 changes: 19 additions & 4 deletions
23
tests/integration-tests/src/test/resources/features/credentials/issue_credentials.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,21 +1,36 @@ | ||
@RFC0453 @AIP20 | ||
Feature: Issue Credentials Protocol | ||
|
||
Scenario: Issuing credential with published PRISM DID to unpublished PRISM DID | ||
Scenario: Issuing credential with published PRISM DID | ||
Given Acme and Bob have an existing connection | ||
When Acme creates unpublished DID | ||
And He publishes DID to ledger | ||
And Bob creates unpublished DID | ||
And Acme offers a credential to Bob with "short" form DID | ||
And Bob receives the credential offer and accepts | ||
And Bob receives the credential offer | ||
And Bob accepts credential offer for JWT | ||
And Acme issues the credential | ||
Then Bob receives the issued credential | ||
|
||
Scenario: Issuing credential with unpublished PRISM DID to unpublished PRISM DID | ||
Scenario: Issuing credential with unpublished PRISM DID | ||
Given Acme and Bob have an existing connection | ||
When Acme creates unpublished DID | ||
And Bob creates unpublished DID | ||
And Acme offers a credential to Bob with "long" form DID | ||
And Bob receives the credential offer and accepts | ||
And Bob receives the credential offer | ||
And Bob accepts credential offer for JWT | ||
And Acme issues the credential | ||
Then Bob receives the issued credential | ||
|
||
Scenario: Issuing anoncred with published PRISM DID | ||
Given Acme and Bob have an existing connection | ||
When Acme creates unpublished DID | ||
And He publishes DID to ledger | ||
And Bob creates unpublished DID | ||
And Acme creates anoncred schema | ||
And Acme creates anoncred credential definition | ||
And Acme offers anoncred to Bob | ||
And Bob receives the credential offer | ||
And Bob accepts credential offer for anoncred | ||
And Acme issues the credential | ||
Then Bob receives the issued credential |