Integration Testing Guide

Integration Certification

All integration partners must successfully certification process prior to deploying an integration to production. The certification process validates connectivity, message structure, functional behavior, and production readiness.

Review the requirements for each testing phase outlined below. If any requirements cannot be met, notify the IDeaS Integration Team as early as possible.

Note
As part of the Client ID and Client Secret provisioning process, IDeaS will provide:

Access to a test RMS environment

The list of required Dynamic Test cases

Interim Testing: Connectivity & Payload Validation

IDeaS provides access to a test RMS environment throughout the development phase.

Before proceeding to Dynamic Testing, your integration must be able to:

Send all planned message types
Receive valid acknowledgements
Resolve, suppress, or review any errors returned

Testing must also include scenarios that require special handling, such as:

Shared reservations
Multi‑unit reservations

For additional context, refer to the Reservation Concepts documentation.

Dynamic Testing: Functional Validation

Dynamic Testing validates that your integration correctly supports the functional behavior expected for the implemented message formats.

Prior to certification testing, you must complete all Dynamic Test cases applicable to your system. These test cases confirm that data is interpreted and reported correctly based on the agreed integration scope.

Note
Required test cases vary based on the functionality implemented and the overall integration scope.

Certification Testing

Once Dynamic Testing is complete, notify the IDeaS Integration Team of the planned start date for certification testing and the initial data synchronization.

Before testing begins, communicate any known constraints—such as historical data limitations—to the Integration Team.

Certification Data Requirements

Certification testing is expected to simulate:

A production cold start
Ongoing daily processing
A continuous testing period of up to seven (7) consecutive days

Review the Data Frequency Guide and notify IDeaS if any data requirements cannot be fulfilled.

Note
If Virtual Suites functionality is included, two cycles of certifications are required:

Certification excluding Virtual Suites data (base integration)

Certification including Virtual Suites data (dependency on base integration passing)

Upon successful completion of certification testing in a test environment, IDeaS will issue a Conditional Certification. Full certification requires completion of a Production Beta.

Production Beta

A mutually shared client, identified prior to or early in development, is required to serve as the Production Beta site.

The conditionally certified integration must be deployed to the PMS/CRS production environment to support the Production Beta. The IDeaS Integrations Team will coordinate:

The production data synchronization
Required production client and property configuration details, including:
- ChainCode
- HotelCode
- OAuth Client ID
- OAuth Client Secret

The Production Beta includes a four‑week monitoring period to confirm stable and accurate daily processing. This period may be extended if unresolved issues are identified.

During the Beta period:

IDeaS performs daily data validations to ensure balance and consistency
The requesting party reviews supplied data, including (but not limited to):
- Sold room counts
- Rate values
- Revenue values
- Room type codes
- Rate codes
- Market segments

If integration or data quality issues are identified, you are expected to prioritize corrective deployments. Depending on the issue, a new cold‑start data synchronization may be required. IDeaS will provide guidance and next steps as needed.

Once the Production Beta completes successfully with no outstanding issues, the integration will be declared Generally Available. IDeaS will update the Project Charter and issue an Integration Certificate.