Skip to content

Commit

Permalink
Upd: Add acceptance criteria for decentralised-dataexchange/bb-consen…
Browse files Browse the repository at this point in the history
…t-api#612

Signed-off-by: George J Padayatti <[email protected]>
  • Loading branch information
georgepadayatti committed Jan 10, 2024
1 parent c74aca5 commit 5ae97a6
Show file tree
Hide file tree
Showing 2 changed files with 53 additions and 216 deletions.
216 changes: 0 additions & 216 deletions gherkin/features/issue_612/issue_610.feature

This file was deleted.

53 changes: 53 additions & 0 deletions gherkin/features/issue_612/issue_612.feature
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`


0 comments on commit 5ae97a6

Please sign in to comment.