-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Upd: Add acceptance criteria for decentralised-dataexchange/bb-consen…
…t-api#612 Signed-off-by: George J Padayatti <[email protected]>
- Loading branch information
1 parent
c74aca5
commit 5ae97a6
Showing
2 changed files
with
53 additions
and
216 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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,53 @@ | ||
@govstack | ||
@critical | ||
@allure.issue:https://github.com/decentralised-dataexchange/bb-consent-api/issues/612 | ||
@allure.label.author:George | ||
@allure.label.as_id:612 | ||
Feature: Revisions | ||
Changes to align with GovStack specifications. | ||
Following conditions should be satisfied in the revision | ||
- Contain `authorizedByOther` field | ||
- Value of `schemaName` field should be the following: DataAgreement, Policy, ConsentRecord | ||
- Remove the following fields from `serializedSnapshot` - `id`, `predecessorHash` and `predecessorSignature` | ||
|
||
@positive | ||
Scenario: Data agreement revision | ||
When I list all revisions for a data agreement with id "<dataAgreementId>" | ||
Then It returns a list of revisions. Returned revision contains `authorizedByOther` field | ||
And Value of `schemaName` field is DataAgreement | ||
And `serializedSnapshot` doesn't contain `id`, `predecessorHash` and `predecessorSignature` | ||
|
||
Examples: | ||
| dataAgreementId | | ||
| 1 | | ||
|
||
@positive | ||
Scenario: Policy revision | ||
When I list all revisions for a policy with id "<policyId>" | ||
Then It returns a list of revisions. Returned revision contains `authorizedByOther` field | ||
And Value of `schemaName` field is Policy | ||
And `serializedSnapshot` doesn't contain `id`, `predecessorHash` and `predecessorSignature` | ||
|
||
Examples: | ||
| policyId | | ||
| 1 | | ||
|
||
@positive | ||
Scenario: Consent record revision | ||
When I read latest consent record with id "<consentRecordId>" for verification | ||
Then It returns a consent record and a revision. Returned revision contains `authorizedByOther` field | ||
And Value of `schemaName` field is ConsentRecord | ||
And `serializedSnapshot` doesn't contain `id`, `predecessorHash` and `predecessorSignature` | ||
|
||
Examples: | ||
| consentRecordId | | ||
| 1 | | ||
|
||
@positive | ||
Scenario: Auto-generated revision during create data agreement | ||
When I create a data agreement | ||
Then It returns the created data agreement and a revision. Returned revision contains `authorizedByOther` field | ||
And Value of `schemaName` field is DataAgreement | ||
And `serializedSnapshot` doesn't contain `id`, `predecessorHash` and `predecessorSignature` | ||
|
||
|