-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CME-109: Update CaseEventToFields tab to include NullifyByDefault as …
…a new column (#1517) * CME-109: Update CaseEventToFields tab to include NullifyByDefault as a new column * CME-109: Update CaseEventToFields tab to include NullifyByDefault as a new column * CME-109: Fix functional test cases * CME-109: Fix functional test cases * CME-109: Fix functional test cases * CME-109: Update test definitions version * CME-109: Update test definitions version * CME-109: Update test definitions version * CME-109: Update test definitions version * CME-109: Fix functional test cases * CME-109: Change data store host * CME-109: Change data store host * CME-109: Change data store host * CME-109: update test definitions version * CME-109: update test definitions version * CME-109: fix test failures * CME-109: fix test failures * CME-109: fix test failures --------- Co-authored-by: Ila Patel <[email protected]>
- Loading branch information
1 parent
99d2147
commit 843130d
Showing
26 changed files
with
1,248 additions
and
66 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
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
57 changes: 57 additions & 0 deletions
57
aat/src/aat/resources/features/F-112 New NullifyByDefault Column/F-112.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,57 @@ | ||
@F-112 | ||
Feature: F-112: New NullifyByDefault Column | ||
|
||
Background: | ||
Given an appropriate test context as detailed in the test data source | ||
|
||
@S-112.1 | ||
Scenario: Import definition file with new field NullifyByDefault set to Yes | ||
Given a user with [an active profile in CCD and with CCD-import role] | ||
When a request is prepared with appropriate values | ||
And the request [contains a definition file that contains NullifyByDefault new field and NullifyByDefault is set to Yes] | ||
And it is submitted to call the [Import definition file] operation of [CCD Definition Store] | ||
And the response [has the 200 OK code] | ||
Then a positive response is received | ||
And the response has all other details as expected | ||
|
||
@S-112.2 | ||
Scenario: Import definition file with new field NullifyByDefault set to No | ||
Given a user with [an active profile in CCD and with CCD-import role] | ||
When a request is prepared with appropriate values | ||
And the request [contains a definition file that contains NullifyByDefault new field and NullifyByDefault is set to No] | ||
And the request [contains a definition file that contains DefaultValue field has a value set] | ||
And it is submitted to call the [Import definition file] operation of [CCD Definition Store] | ||
And the response [has the 200 OK code] | ||
Then a positive response is received | ||
And the response has all other details as expected | ||
|
||
@S-112.3 | ||
Scenario: Return error when DefaultValue has a value and NullifyByDefault is set to Yes | ||
Given a user with [an active profile in CCD and with CCD-import role] | ||
When a request is prepared with appropriate values | ||
And the request [contains a definition file that contains NullifyByDefault new field and NullifyByDefault is set to Yes] | ||
And the request [contains a definition file that contains DefaultValue field has a value set] | ||
And it is submitted to call the [Import definition file] operation of [CCD Definition Store] | ||
And the response [has the 400 Bad Request code] | ||
Then a negative response is received | ||
|
||
@S-112.4 | ||
Scenario: Return success when DefaultValue has a value and NullifyByDefault is set to No | ||
Given a user with [an active profile in CCD and with CCD-import role] | ||
When a request is prepared with appropriate values | ||
And the request [contains a definition file that contains NullifyByDefault new field and NullifyByDefault is set to No] | ||
And the request [contains a definition file that contains DefaultValue field has a value set] | ||
And it is submitted to call the [Import definition file] operation of [CCD Definition Store] | ||
And the response [has the 200 OK code] | ||
Then a positive response is received | ||
And the response has all other details as expected | ||
|
||
@S-112.5 | ||
Scenario: Retrieve CaseEventToFields values | ||
Given a user with [an active profile in CCD] | ||
When a request is prepared with appropriate values | ||
And the request [contains a valid jurisdiction id] | ||
And the request [contains a valid caseType id] | ||
And it is submitted to call the [Get Case Type Details] operation of [CCD Definition Store] | ||
Then the response [has the 200 OK code] | ||
And the response [contains case type details] |
Oops, something went wrong.