Testing and Certification

Interim Tests

IDeaS will provide a test RMS for dynamic testing throughout the development phase. Before moving to Dynamic Tests, you should be able to send all messages that will be implemented, receive acknowledgement, and have removed or discussed the errors received. This should include covering special handling requirements like reservation shares or multi-unit reservations. See Reservation Concepts for further details.

We suggest that you use a copy of a production system to generate the messages to ensure that you have tested the most common data situations.

Dynamic Tests

To prepare for certification testing, you must complete the Dynamic Test cases that are applicable to your system. Complete these test cases prior to certification testing. The test cases will validate that the functionality provided through the message format is as expected.

Note

IDeaS will provide access to a test RMS and the list of Dynamic Test cases as part of the Client ID and Client Secret provisioning process. These Dynamic test cases will vary depending on the functionality that you decide to implement and the scope of the integration.

Certification Testing

Once you are ready to complete certification testing, notify the IDeaS Integration Team about the date that the sync of data will start. Communicate any restrictions to the requirements to the IDeaS Integrations Team, including historical limitations, prior to beginning certification testing.

Certification Data Requirements:

Certification testing requirements are expected to simulate production cold-start and daily processing for up to 7 consecutive days. Review the Data Frequency Guidelines and advise the IDeaS Integration Team if you cannot meet any of the data requirements outlined in the testing guide.

Note

If you are testing Component Room functionality, two certifications are required. The first is for the non-Component Room data; the second is to include Component Rooms in the data.

Once Certification Testing is completed in a test environment, IDeaS will award a Conditional Certification. Full Certification is dependent upon successfully completing a Production Beta.

Production Beta

A mutual client, identified either before or early in the integration development, will be the Integrations Production Beta that is required to complete a full certification of the integration.

IDeaS expects that the conditionally certified integration is deployed to the PMS/CRS production environment to support the Production Beta installation. IDeaS Integrations will work with you to complete the data sync and will share any required Client/Property configurations prior, such as the ChainCode, HotelCode, and OAuth client secret and client ID. During the Production Beta, a period of 4 weeks is set to monitor that daily processing is occurring without issues. If there are any on-going issues, the Beta period may be extended.

During the Beta period, IDeaS Integrations will complete data validations to ensure that data received from the receiving system is balancing from day to day. The Request client reviews the supplied data, including, but not limited to, validating solds, rate values, revenues, room type codes, rate codes, and market segments.

If any issues concerning integration or data quality are identified during the Beta period, it is your responsibility to deploy fixes as a priority. A new cold-start data sync may be needed, depending on the issue. IDeaS Integrations will share requirements, along with the steps to move ahead.

After the Beta period is complete and no further issues are identified, IDeaS will announce the integration to be Generally Available. IDeaS will update the Project Charter and provide an Integrations Certificate to our new Partner.

Note

We highly recommend that we work together to create supporting documentation for configuration requirements within the PMS/CRS specific for the connection to IDeaS RMS. These documents are proven to allow for seamless integrations with less escalations. These guidelines would be shared with clients at the time of installation. Suggested areas of guidance would be Rate Code and Market Segmentation configurations, License Activation, Virtual Suites configuration, mapping requirements, and support escalation.