-
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.
Add #9 Align Gherkin scenarios with Test Protocol and GovStack Open A…
…PI spec
- Loading branch information
1 parent
a119ae0
commit 87f4da9
Showing
47 changed files
with
2,027 additions
and
1,638 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,4 @@ | ||
api-backup.json | ||
api-dev-tests.json | ||
temp/ | ||
temp/ | ||
env |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
17 changes: 17 additions & 0 deletions
17
features/admin_dashboard/admin_logging/admin_logging.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 |
---|---|---|
@@ -0,0 +1,17 @@ | ||
Feature: Admin Log Viewing | ||
|
||
Background: | ||
Given an organization admin for Data4Diabetes organization | ||
And the admin is logged into the Admin dashboard | ||
|
||
Scenario: View security log for admin function | ||
When the admin clicks on the "view admin function" | ||
Then the admin should be able to view security log functions | ||
|
||
Scenario: View webhook log for admin function | ||
When the admin clicks on the "view admin function" | ||
Then the admin should be able to view webhook log functions | ||
|
||
Scenario: View API log for admin function | ||
When the admin clicks on the "view admin function" | ||
Then the admin should be able to view API calls log functions |
45 changes: 45 additions & 0 deletions
45
features/admin_dashboard/data_agreement/create_data_agreement.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 |
---|---|---|
@@ -0,0 +1,45 @@ | ||
Feature: Data Agreement Creation | ||
|
||
Background: | ||
Given an organization admin for Data4Diabetes organization | ||
And the admin is logged into the Admin dashboard | ||
|
||
Scenario: Create Data Agreement with new data policy | ||
When the admin chooses a new data policy | ||
And creates a data agreement in draft mode | ||
Then the data agreement should be in draft mode with version 1.0.0 | ||
|
||
Scenario: Create Data Agreement with existing data policy | ||
When the admin chooses an existing data policy template | ||
And creates a data agreement in draft mode | ||
Then the data agreement should be in draft mode with version 1.0.0 | ||
|
||
Scenario: Create Data Agreement with updated data fields | ||
When the admin chooses an existing data policy template | ||
And updates one or two fields to create a data agreement in draft mode | ||
Then the data agreement should be in draft mode with version 1.0.0 | ||
|
||
Scenario: Create a new Data Agreement | ||
When the admin chooses a new data policy to create a data agreement | ||
And creates a data agreement | ||
Then the data agreement should be created with version 1.0.0 | ||
|
||
Scenario: Create a new Data Agreement to publish | ||
When the admin chooses an existing data policy template | ||
And creates a data agreement | ||
Then the data agreement should be created with version 1.0.0 | ||
|
||
Scenario: Create Data Agreement to publish | ||
When the admin chooses an existing data policy template | ||
And updates one or two fields to create a data agreement | ||
Then the data agreement should be created with version 1.0.0 | ||
|
||
Scenario: Create several Data Agreements | ||
When the admin creates several data agreements in one transaction | ||
And uses CLI command | ||
Then the multiple data agreements should be created | ||
|
||
Scenario: Create an Agreement with non-consent basis | ||
When the admin chooses a lawful basis other than consent | ||
And create a data agreement | ||
Then the data agreement should be created with version 1.0.0 |
13 changes: 13 additions & 0 deletions
13
features/admin_dashboard/data_agreement/delete_data_agreement.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 |
---|---|---|
@@ -0,0 +1,13 @@ | ||
Feature: Deleting Data Agreements | ||
|
||
Background: | ||
Given an organization admin for Data4Diabetes organization | ||
And the admin is logged into the Admin dashboard | ||
|
||
Scenario: Delete Data Agreement | ||
When the admin deletes a data agreement | ||
Then the data agreement should be deleted | ||
|
||
Scenario: Delete draft Data Agreement | ||
When the admin deletes a draft data agreement | ||
Then the data agreement should be deleted |
13 changes: 13 additions & 0 deletions
13
features/admin_dashboard/data_agreement/filter_data_agreements.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 |
---|---|---|
@@ -0,0 +1,13 @@ | ||
Feature: Filtering Data Agreements | ||
|
||
Background: | ||
Given an organization admin for Data4Diabetes organization | ||
And the admin is logged into the Admin dashboard | ||
|
||
Scenario: Filter published Data Agreement | ||
When the admin clicks the "Published" radio button | ||
Then the Published data agreements should be shown | ||
|
||
Scenario: Filter Data Agreement | ||
When the admin clicks the "All" radio button | ||
Then the All data agreements should be shown |
46 changes: 46 additions & 0 deletions
46
features/admin_dashboard/data_agreement/update_data_agreement.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 |
---|---|---|
@@ -0,0 +1,46 @@ | ||
Feature: Updating Data Agreements | ||
|
||
Background: | ||
Given an organization admin for Data4Diabetes organization | ||
And the admin is logged into the Admin dashboard | ||
|
||
Scenario: Update Data Agreement with None mode | ||
When the admin clicks on the update icon | ||
And updates data agreement as none mode | ||
And clicks publish | ||
Then the data agreement should be updated | ||
|
||
Scenario: Update Data Agreement as DS | ||
When the admin clicks on the update icon | ||
And updates data agreement as DS | ||
And clicks publish | ||
Then the data agreement should be updated | ||
|
||
Scenario: Update Data Agreement as DUS | ||
When the admin clicks on the update icon | ||
And updates data agreement as DUS | ||
And clicks publish | ||
Then the data agreement should be updated | ||
|
||
Scenario: Update draft Data Agreement | ||
When the admin clicks on the update icon | ||
And updates only the fields permitted to change | ||
And clicks save | ||
Then the data agreement should be updated | ||
|
||
Scenario: Update new Data Agreement | ||
When the admin clicks on the update icon | ||
And updates only the fields permitted to change | ||
And clicks save | ||
Then the data agreement should be updated | ||
|
||
Scenario: Update Data Agreement as Draft mode | ||
When the admin clicks on the update icon | ||
And updates only the fields permitted to change | ||
And clicks save | ||
Then the data agreement should be updated | ||
|
||
Scenario: Update delete attribute in Data Agreement | ||
When the admin clicks on the update icon | ||
And deletes an attribute in data agreement | ||
Then the data agreement should be updated |
25 changes: 25 additions & 0 deletions
25
features/admin_dashboard/data_agreement/view_data_agreement.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 |
---|---|---|
@@ -0,0 +1,25 @@ | ||
Feature: Data Agreement Viewing | ||
|
||
Background: | ||
Given an organization admin for Data4Diabetes organization | ||
And the admin is logged into the Admin dashboard | ||
|
||
Scenario: View publish Data Agreement | ||
When the admin clicks on the eye or view icon | ||
And views the data agreement table | ||
Then the admin should be able to view the data agreement | ||
|
||
Scenario: View Data Agreement | ||
When the admin clicks on the eye or view icon | ||
And views the data agreement table | ||
Then the admin should be able to view the data agreement | ||
|
||
Scenario: View draft Data Agreement | ||
When the admin clicks on the eye or view icon | ||
And views the data agreement | ||
Then the admin should be able to view the draft data agreement | ||
|
||
Scenario: View revision history of Data Agreement | ||
When the admin clicks on the version icon | ||
And views the version for the agreements list | ||
Then the admin should be able to view all version history for data agreement |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
13 changes: 13 additions & 0 deletions
13
features/admin_dashboard/global_data_policy/global_data_policy.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 |
---|---|---|
@@ -0,0 +1,13 @@ | ||
Feature: Global Data Policy | ||
|
||
Background: | ||
Given an organization admin for Data4Diabetes organization | ||
And the admin is logged into the Admin dashboard | ||
|
||
Scenario: Create Global Policy Configuration | ||
When the admin creates global policy configuration | ||
Then the global policy configuration should be created | ||
|
||
Scenario: Update Global Policy Configuration | ||
When the admin updates global policy configuration | ||
Then the global policy configuration should be updated |
Oops, something went wrong.