Merge pull request #2662 from ianco/anoncreds-int-tests-2

Tweak scope of GHA integration tests
openwallet-foundation · Dec 8, 2023 · 2adeb8e · 2adeb8e
2 parents b055b78 + 90ed8ad
commit 2adeb8e
Show file tree

Hide file tree

Showing 3 changed files with 129 additions and 23 deletions.
diff --git a/demo/features/0160-connection.feature b/demo/features/0160-connection.feature
@@ -1,6 +1,6 @@
 Feature: RFC 0160 Aries agent connection functions
 
-   @T001-RFC0160 @GHA
+   @T001-RFC0160
    Scenario Outline: establish a connection between two agents
       Given we have "2" agents
          | name  | role    | capabilities        |
@@ -11,13 +11,18 @@ Feature: RFC 0160 Aries agent connection functions
       Then "Acme" has an active connection
       And "Bob" has an active connection
 
+      @GHA @WalletType_Askar
       Examples:
          | Acme_capabilities                      | Bob_capabilities          |
          | --public-did                           |                           |
          | --public-did --did-exchange            | --did-exchange            |
          | --public-did --mediation               | --mediation               |
          | --public-did --multitenant             | --multitenant             |
          | --public-did --mediation --multitenant | --mediation --multitenant |
+
+      @GHA @WalletType_Askar_AnonCreds
+      Examples:
+         | Acme_capabilities                      | Bob_capabilities          |
          | --public-did --wallet-type askar-anoncreds | --wallet-type askar-anoncreds |
          | --public-did --wallet-type askar-anoncreds |                               |
          | --public-did                           | --wallet-type askar-anoncreds |

diff --git a/demo/features/0453-issue-credential.feature b/demo/features/0453-issue-credential.feature
@@ -1,7 +1,7 @@
 @RFC0453
 Feature: RFC 0453 Aries agent issue credential
 
-  @T003-RFC0453 @GHA
+  @T003-RFC0453
   Scenario Outline: Issue a credential with the Issuer beginning with an offer
     Given we have "2" agents
       | name  | role    | capabilities        |
@@ -12,17 +12,22 @@ Feature: RFC 0453 Aries agent issue credential
     When "Acme" offers a credential with data <Credential_data>
     Then "Bob" has the credential issued
 
+    @GHA @WalletType_Askar
     Examples:
        | Acme_capabilities                      | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did                           |                           | driverslicense | Data_DL_NormalizedValues |
        | --public-did --did-exchange            | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
        | --public-did --mediation               | --mediation               | driverslicense | Data_DL_NormalizedValues |
        | --public-did --multitenant             | --multitenant             | driverslicense | Data_DL_NormalizedValues |
+
+    @GHA @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                      | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --wallet-type askar-anoncreds | --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
        | --public-did --wallet-type askar-anoncreds |                               | driverslicense | Data_DL_NormalizedValues |
        | --public-did                           | --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
 
-  @T003-RFC0453 @GHA
+  @T003-RFC0453
   Scenario Outline: Holder accepts a deleted credential offer
     Given we have "2" agents
       | name  | role    | capabilities        |
@@ -33,15 +38,24 @@ Feature: RFC 0453 Aries agent issue credential
     And "Acme" offers and deletes a credential with data <Credential_data>
     Then "Bob" has the exchange abandoned
 
+    @GHA @WalletType_Askar
     Examples:
        | Acme_capabilities                      | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did                           |                           | driverslicense | Data_DL_NormalizedValues |
+
+    @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                      | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --wallet-type askar-anoncreds | --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
-       #| --public-did --did-exchange            | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
-       #| --public-did --mediation               | --mediation               | driverslicense | Data_DL_NormalizedValues |
-       #| --public-did --multitenant             | --multitenant             | driverslicense | Data_DL_NormalizedValues |
 
-  @T003-RFC0453 @GHA
+    @WalletType_Askar
+    Examples:
+       | Acme_capabilities                      | Bob_capabilities          | Schema_name    | Credential_data          |
+       | --public-did --did-exchange            | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
+       | --public-did --mediation               | --mediation               | driverslicense | Data_DL_NormalizedValues |
+       | --public-did --multitenant             | --multitenant             | driverslicense | Data_DL_NormalizedValues |
+
+  @T003-RFC0453
   Scenario Outline: Issue a credential with the holder sending a request
     Given we have "2" agents
       | name  | role    | capabilities        |
@@ -51,16 +65,25 @@ Feature: RFC 0453 Aries agent issue credential
     And "Acme" is ready to issue a credential for <Schema_name>
     When "Bob" requests a credential with data <Credential_data> from "Acme" it fails
 
+    @GHA @WalletType_Askar
     Examples:
        | Acme_capabilities                      | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did                           |                           | driverslicense | Data_DL_NormalizedValues |
+
+    @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                      | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --wallet-type askar-anoncreds | --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
-       #| --public-did --did-exchange            | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
-       #| --public-did --mediation               | --mediation               | driverslicense | Data_DL_NormalizedValues |
-       #| --public-did --multitenant             | --multitenant             | driverslicense | Data_DL_NormalizedValues |
+
+    @WalletType_Askar
+    Examples:
+       | Acme_capabilities                      | Bob_capabilities          | Schema_name    | Credential_data          |
+       | --public-did --did-exchange            | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
+       | --public-did --mediation               | --mediation               | driverslicense | Data_DL_NormalizedValues |
+       | --public-did --multitenant             | --multitenant             | driverslicense | Data_DL_NormalizedValues |
 
 
-  @T003.1-RFC0453 @GHA
+  @T003.1-RFC0453
   Scenario Outline: Holder accepts a deleted json-ld credential offer
     Given we have "2" agents
       | name  | role    | capabilities        |
@@ -73,15 +96,24 @@ Feature: RFC 0453 Aries agent issue credential
     Then "Bob" has the json-ld credential issued
     And "Acme" has the exchange completed
 
+    @GHA @WalletType_Askar
     Examples:
        | Acme_capabilities                                   | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --cred-type json-ld                    |                           | driverslicense | Data_DL_NormalizedValues |
+
+    @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                                   | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --cred-type json-ld --wallet-type askar-anoncreds | --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
-       # | --public-did --cred-type json-ld --did-exchange     | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
-       # | --public-did --cred-type json-ld --mediation        | --mediation               | driverslicense | Data_DL_NormalizedValues |
-       # | --public-did --cred-type json-ld --multitenant      | --multitenant             | driverslicense | Data_DL_NormalizedValues |
 
-  @T003.1-RFC0453 @GHA
+    @WalletType_Askar
+    Examples:
+       | Acme_capabilities                                   | Bob_capabilities          | Schema_name    | Credential_data          |
+       | --public-did --cred-type json-ld --did-exchange     | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
+       | --public-did --cred-type json-ld --mediation        | --mediation               | driverslicense | Data_DL_NormalizedValues |
+       | --public-did --cred-type json-ld --multitenant      | --multitenant             | driverslicense | Data_DL_NormalizedValues |
+
+  @T003.1-RFC0453
   Scenario Outline: Issue a json-ld credential with the Issuer beginning with an offer
     Given we have "2" agents
       | name  | role    | capabilities        |
@@ -93,19 +125,28 @@ Feature: RFC 0453 Aries agent issue credential
     When "Acme" offers "Bob" a json-ld credential with data <Credential_data>
     Then "Bob" has the json-ld credential issued
 
+    @GHA @WalletType_Askar
     Examples:
        | Acme_capabilities                                   | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --cred-type json-ld                    |                           | driverslicense | Data_DL_NormalizedValues |
        | --public-did --cred-type json-ld --did-exchange     | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
        | --public-did --cred-type json-ld --mediation        | --mediation               | driverslicense | Data_DL_NormalizedValues |
        | --public-did --cred-type json-ld --multitenant      | --multitenant             | driverslicense | Data_DL_NormalizedValues |
+
+    @GHA @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                                   | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --cred-type json-ld --wallet-type askar-anoncreds | --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
        | --public-did --cred-type json-ld --did-exchange --wallet-type askar-anoncreds | --did-exchange --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
+
+    @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                                   | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --cred-type json-ld --mediation --wallet-type askar-anoncreds | --mediation --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
        | --public-did --cred-type json-ld --multitenant --wallet-type askar-anoncreds | --multitenant --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
 
 
-  @T003.1-RFC0453 @GHA
+  @T003.1-RFC0453
   Scenario Outline: Issue a json-ld credential with the holder beginning with a request
     Given we have "2" agents
       | name  | role    | capabilities        |
@@ -117,16 +158,21 @@ Feature: RFC 0453 Aries agent issue credential
     When "Bob" requests a json-ld credential with data <Credential_data> from "Acme"
     Then "Bob" has the json-ld credential issued
 
+    @GHA @WalletType_Askar
     Examples:
        | Acme_capabilities                                   | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --cred-type json-ld                    |                           | driverslicense | Data_DL_NormalizedValues |
        | --public-did --cred-type json-ld --did-exchange     | --did-exchange            | driverslicense | Data_DL_NormalizedValues |
        | --public-did --cred-type json-ld --mediation        | --mediation               | driverslicense | Data_DL_NormalizedValues |
        | --public-did --cred-type json-ld --multitenant      | --multitenant             | driverslicense | Data_DL_NormalizedValues |
+
+    @GHA @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                                   | Bob_capabilities          | Schema_name    | Credential_data          |
        | --public-did --cred-type json-ld --wallet-type askar-anoncreds | --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
 
 
-  @T004-RFC0453 @GHA
+  @T004-RFC0453
   Scenario Outline: Issue a credential with revocation, with the Issuer beginning with an offer, and then revoking the credential
     Given we have "2" agents
       | name  | role    | capabilities        |
@@ -137,11 +183,16 @@ Feature: RFC 0453 Aries agent issue credential
     Then "Acme" revokes the credential
     And "Bob" has the credential issued
 
+    @GHA @WalletType_Askar
     Examples:
        | Acme_capabilities                        | Bob_capabilities  | Schema_name    | Credential_data          |
        | --revocation --public-did                |                   | driverslicense | Data_DL_NormalizedValues |
        | --revocation --public-did --did-exchange | --did-exchange    | driverslicense | Data_DL_NormalizedValues |
        | --revocation --public-did --multitenant  | --multitenant     | driverslicense | Data_DL_NormalizedValues |
+
+    @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                        | Bob_capabilities  | Schema_name    | Credential_data          |
        | --revocation --public-did --wallet-type askar-anoncreds | --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |
 
   @T004.1-RFC0453
@@ -155,7 +206,12 @@ Feature: RFC 0453 Aries agent issue credential
     Then "Acme" revokes the credential
     And "Bob" has the credential issued
 
+    @WalletType_Askar
     Examples:
        | Acme_capabilities                        | Bob_capabilities  | Schema_name    | Credential_data          |
        | --revocation --public-did --mediation    | --mediation       | driverslicense | Data_DL_NormalizedValues |
+
+    @WalletType_Askar_AnonCreds
+    Examples:
+       | Acme_capabilities                        | Bob_capabilities  | Schema_name    | Credential_data          |
        | --revocation --public-did --mediation --wallet-type askar-anoncreds | --mediation --wallet-type askar-anoncreds | driverslicense | Data_DL_NormalizedValues |