-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
#104: Added newly generated artifacts
- Loading branch information
darnjo
committed
Sep 5, 2023
1 parent
6afa3b5
commit f04341f
Showing
68 changed files
with
18,925 additions
and
0 deletions.
There are no files selected for viewing
53 changes: 53 additions & 0 deletions
53
...ain/java/org/reso/certification/features/data-dictionary/v1-7/contactlistingnotes.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,53 @@ | ||
# This file was autogenerated on: 20230905094351998 | ||
Feature: ContactListingNotes | ||
|
||
Background: | ||
Given a RESOScript or Metadata file are provided | ||
When a RESOScript file is provided | ||
Then Client Settings and Parameters can be read from the RESOScript | ||
And a test container was successfully created from the given RESOScript file | ||
And the test container uses an Authorization Code or Client Credentials for authentication | ||
And valid metadata were retrieved from the server | ||
When a metadata file is provided | ||
Then a test container was successfully created from the given metadata file | ||
And valid metadata are loaded into the test container | ||
|
||
@ContactListingNotes @dd-1.7 | ||
Scenario: ContactKey | ||
When "ContactKey" exists in the "ContactListingNotes" metadata | ||
Then "ContactKey" MUST be "String" data type | ||
And "ContactKey" length SHOULD be equal to the RESO Suggested Max Length of 255 | ||
|
||
@ContactListingNotes @dd-1.7 | ||
Scenario: ContactListingNotesKey | ||
When "ContactListingNotesKey" exists in the "ContactListingNotes" metadata | ||
Then "ContactListingNotesKey" MUST be "String" data type | ||
And "ContactListingNotesKey" length SHOULD be equal to the RESO Suggested Max Length of 255 | ||
|
||
@ContactListingNotes @dd-1.7 | ||
Scenario: ListingId | ||
When "ListingId" exists in the "ContactListingNotes" metadata | ||
Then "ListingId" MUST be "String" data type | ||
And "ListingId" length SHOULD be equal to the RESO Suggested Max Length of 255 | ||
|
||
@ContactListingNotes @dd-1.7 | ||
Scenario: ListingKey | ||
When "ListingKey" exists in the "ContactListingNotes" metadata | ||
Then "ListingKey" MUST be "String" data type | ||
And "ListingKey" length SHOULD be equal to the RESO Suggested Max Length of 255 | ||
|
||
@ContactListingNotes @dd-1.7 | ||
Scenario: ModificationTimestamp | ||
When "ModificationTimestamp" exists in the "ContactListingNotes" metadata | ||
Then "ModificationTimestamp" MUST be "Timestamp" data type | ||
|
||
@ContactListingNotes @dd-1.7 | ||
Scenario: NoteContents | ||
When "NoteContents" exists in the "ContactListingNotes" metadata | ||
Then "NoteContents" MUST be "String" data type | ||
And "NoteContents" length SHOULD be equal to the RESO Suggested Max Length of 500 | ||
|
||
@ContactListingNotes @dd-1.7 | ||
Scenario: NotedBy | ||
When "NotedBy" exists in the "ContactListingNotes" metadata | ||
Then "NotedBy" MUST be "Single Enumeration" data type |
108 changes: 108 additions & 0 deletions
108
src/main/java/org/reso/certification/features/data-dictionary/v1-7/contactlistings.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,108 @@ | ||
# This file was autogenerated on: 20230905094351998 | ||
Feature: ContactListings | ||
|
||
Background: | ||
Given a RESOScript or Metadata file are provided | ||
When a RESOScript file is provided | ||
Then Client Settings and Parameters can be read from the RESOScript | ||
And a test container was successfully created from the given RESOScript file | ||
And the test container uses an Authorization Code or Client Credentials for authentication | ||
And valid metadata were retrieved from the server | ||
When a metadata file is provided | ||
Then a test container was successfully created from the given metadata file | ||
And valid metadata are loaded into the test container | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: AgentNotesUnreadYN | ||
When "AgentNotesUnreadYN" exists in the "ContactListings" metadata | ||
Then "AgentNotesUnreadYN" MUST be "Boolean" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ClassName | ||
When "ClassName" exists in the "ContactListings" metadata | ||
Then "ClassName" MUST be "Single Enumeration" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ContactKey | ||
When "ContactKey" exists in the "ContactListings" metadata | ||
Then "ContactKey" MUST be "String" data type | ||
And "ContactKey" length SHOULD be equal to the RESO Suggested Max Length of 255 | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ContactListingPreference | ||
When "ContactListingPreference" exists in the "ContactListings" metadata | ||
Then "ContactListingPreference" MUST be "Single Enumeration" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ContactListingsKey | ||
When "ContactListingsKey" exists in the "ContactListings" metadata | ||
Then "ContactListingsKey" MUST be "String" data type | ||
And "ContactListingsKey" length SHOULD be equal to the RESO Suggested Max Length of 255 | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ContactLoginId | ||
When "ContactLoginId" exists in the "ContactListings" metadata | ||
Then "ContactLoginId" MUST be "String" data type | ||
And "ContactLoginId" length SHOULD be equal to the RESO Suggested Max Length of 25 | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ContactNotesUnreadYN | ||
When "ContactNotesUnreadYN" exists in the "ContactListings" metadata | ||
Then "ContactNotesUnreadYN" MUST be "Boolean" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: DirectEmailYN | ||
When "DirectEmailYN" exists in the "ContactListings" metadata | ||
Then "DirectEmailYN" MUST be "Boolean" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: LastAgentNoteTimestamp | ||
When "LastAgentNoteTimestamp" exists in the "ContactListings" metadata | ||
Then "LastAgentNoteTimestamp" MUST be "Timestamp" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: LastContactNoteTimestamp | ||
When "LastContactNoteTimestamp" exists in the "ContactListings" metadata | ||
Then "LastContactNoteTimestamp" MUST be "Timestamp" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ListingId | ||
When "ListingId" exists in the "ContactListings" metadata | ||
Then "ListingId" MUST be "String" data type | ||
And "ListingId" length SHOULD be equal to the RESO Suggested Max Length of 255 | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ListingKey | ||
When "ListingKey" exists in the "ContactListings" metadata | ||
Then "ListingKey" MUST be "String" data type | ||
And "ListingKey" length SHOULD be equal to the RESO Suggested Max Length of 255 | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ListingModificationTimestamp | ||
When "ListingModificationTimestamp" exists in the "ContactListings" metadata | ||
Then "ListingModificationTimestamp" MUST be "Timestamp" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ListingSentTimestamp | ||
When "ListingSentTimestamp" exists in the "ContactListings" metadata | ||
Then "ListingSentTimestamp" MUST be "Timestamp" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ListingViewedYN | ||
When "ListingViewedYN" exists in the "ContactListings" metadata | ||
Then "ListingViewedYN" MUST be "Boolean" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ModificationTimestamp | ||
When "ModificationTimestamp" exists in the "ContactListings" metadata | ||
Then "ModificationTimestamp" MUST be "Timestamp" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: PortalLastVisitedTimestamp | ||
When "PortalLastVisitedTimestamp" exists in the "ContactListings" metadata | ||
Then "PortalLastVisitedTimestamp" MUST be "Timestamp" data type | ||
|
||
@ContactListings @dd-1.7 | ||
Scenario: ResourceName | ||
When "ResourceName" exists in the "ContactListings" metadata | ||
Then "ResourceName" MUST be "Single Enumeration" data type |
Oops, something went wrong.