Certification - Demand

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

Test Scenario
Objective
Expected Outcome
Remarks

Basic Connectivity Check

Validate OTA can send HDI request and receive a valid response

Successful HDI response with no connection error

Confirm endpoint config & credentials

Test Property Retrieval

Validate OTA is able to retrieve content for the test property

HDI response contains full data for test PID

Used for functional validations

All Subscribed Brands Retrieval

Check if content is retrievable for all subscribed brands/PIDs

Content data retrieved for each brand without failure

Ensures all subscribed brand returning valid response

Mandatory Fields Validation

Confirm all required fields are present in the response (e.g., name, address, contact, country, etc.)

No field missing or malformed

Room Types & Descriptions

Validate room-level data: room names, max occupancy, descriptions

Accurate, clean, and complete room info in OTA system

Map 1:1 with HCD values

Amenity Codes Check

Validate all amenity codes (general + room-specific) are included

Amenity mapping is correct and visible on OTA end

Test across various properties

Image and Multimedia Content

Verify image links, room-level media

All images load from ICE Portal/Leonardo match the room

Also check thumbnail

ODDCCN File Retrieval & Access

Verify ODDCCN delta file (daily content update) is accessible & being genrated

OTA confirms file retrieval and parsing success

Check file format, frequency, and structure

Delta File – Triggering HDI Retrieval

Validate that OTA triggers HDI calls for PIDs listed in ODDCCN

HDI fetches happen after parsing delta list

Ensures daily updates are reflected

Deleted/Inactive Property Handling

Ensure OTA gracefully handles properties marked deleted in ODDCCN

OTA removes/inactivates property in their DB

Avoids listing closed properties

Error Code Handling

Simulate invalid PID, malformed XML, etc., to check error handling

Relevant DHISCO error codes received and logged

Must support fallback process

Data Freshness Check

Confirm OTA refreshes content & it reflect in HCD

Updated content reflects within HCD

Test a property with changed data

Content Parity Validation

Cross-verify HCD content with what OTA receives

Room types, descriptions, amenities, brand name match exactly

Needs to be done before sign-off

Environment Setup Confirmation

Verify both UAT and Production environments respond correctly

OTA able to test in UAT and move seamlessly to Prod

Mandatory for rollout

Image Hosting and Timeout Checks

Confirm that image URLs don’t break or expire and load timely

Images URLs must be up to date

Image URLs must be up to date in DB by Image partners

Character Encoding & Language Support

Validate content encoding (UTF-8), special characters, and multilingual support if applicable

No garbled or broken text in OTA UI

Especially important for international content

Max Length Validation

Check OTA can handle long descriptions, room names, amenity details

No truncation or UI breakage

Especially for suites or chain-level data

Unsubscribed Property Behavior

Send HDI call for an unsubscribed property – check response

Proper error returned (e.g., PID07)

OTA should not list non-authorized properties

System Failure Simulation

Simulate outage/unavailable endpoint – check OTA fallback logic

OTA handles gracefully with retry or suppression

Important for production readiness

Last updated