# Certification - Demand

Below are the certification test scenarios followed by Demand partners for Content Retrieval:

<table><thead><tr><th width="217">Test Scenario</th><th width="263">Objective</th><th width="207">Expected Outcome</th><th width="208">Remarks</th></tr></thead><tbody><tr><td>Basic Connectivity Check</td><td>Validate OTA can send HDI request and receive a valid response</td><td>Successful HDI response with no connection error</td><td>Confirm endpoint config &#x26; credentials</td></tr><tr><td>Test Property Retrieval</td><td>Validate OTA is able to retrieve content for the test property</td><td>HDI response contains full data for test PID</td><td>Used for functional validations</td></tr><tr><td>All Subscribed Brands Retrieval</td><td>Check if content is retrievable for all subscribed brands/PIDs</td><td>Content data retrieved for each brand without failure</td><td>Ensures all subscribed brand returning valid response</td></tr><tr><td>Mandatory Fields Validation</td><td>Confirm all required fields are present in the response (e.g., name, address, contact, country, etc.)</td><td>No field missing or malformed</td><td> </td></tr><tr><td>Room Types &#x26; Descriptions</td><td>Validate room-level data: room names, max occupancy, descriptions</td><td>Accurate, clean, and complete room info in OTA system</td><td>Map 1:1 with HCD values</td></tr><tr><td>Amenity Codes Check</td><td>Validate all amenity codes (general + room-specific) are included</td><td>Amenity mapping is correct and visible on OTA end</td><td>Test across various properties</td></tr><tr><td>Image and Multimedia Content</td><td>Verify image links, room-level media</td><td>All images load from ICE Portal/Leonardo match the room</td><td>Also check thumbnail</td></tr><tr><td>ODDCCN File Retrieval &#x26; Access</td><td>Verify ODDCCN delta file (daily content update) is accessible &#x26; being genrated</td><td>OTA confirms file retrieval and parsing success</td><td>Check file format, frequency, and structure</td></tr><tr><td>Delta File – Triggering HDI Retrieval</td><td>Validate that OTA triggers HDI calls for PIDs listed in ODDCCN</td><td>HDI fetches happen after parsing delta list</td><td>Ensures daily updates are reflected</td></tr><tr><td>Deleted/Inactive Property Handling</td><td>Ensure OTA gracefully handles properties marked deleted in ODDCCN</td><td>OTA removes/inactivates property in their DB</td><td>Avoids listing closed properties</td></tr><tr><td>Error Code Handling</td><td>Simulate invalid PID, malformed XML, etc., to check error handling</td><td>Relevant DHISCO error codes received and logged</td><td>Must support fallback process</td></tr><tr><td>Data Freshness Check</td><td>Confirm OTA refreshes content &#x26; it reflect in HCD</td><td>Updated content reflects within HCD</td><td>Test a property with changed data</td></tr><tr><td>Content Parity Validation</td><td>Cross-verify HCD content with what OTA receives</td><td>Room types, descriptions, amenities, brand name match exactly</td><td>Needs to be done before sign-off</td></tr><tr><td>Environment Setup Confirmation</td><td>Verify both UAT and Production environments respond correctly</td><td>OTA able to test in UAT and move seamlessly to Prod</td><td>Mandatory for rollout</td></tr><tr><td>Image Hosting and Timeout Checks</td><td>Confirm that image URLs don’t break or expire and load timely</td><td>Images URLs must be up to date</td><td>Image URLs must be up to date in DB by Image partners</td></tr><tr><td>Character Encoding &#x26; Language Support</td><td>Validate content encoding (UTF-8), special characters, and multilingual support if applicable</td><td>No garbled or broken text in OTA UI</td><td>Especially important for international content</td></tr><tr><td>Max Length Validation</td><td>Check OTA can handle long descriptions, room names, amenity details</td><td>No truncation or UI breakage</td><td>Especially for suites or chain-level data</td></tr><tr><td>Unsubscribed Property Behavior</td><td>Send HDI call for an unsubscribed property – check response</td><td>Proper error returned (e.g., PID07)</td><td>OTA should not list non-authorized properties</td></tr><tr><td>System Failure Simulation</td><td>Simulate outage/unavailable endpoint – check OTA fallback logic</td><td>OTA handles gracefully with retry or suppression</td><td>Important for production readiness</td></tr></tbody></table>