Sunteți pe pagina 1din 1

Testing

Host Functionality Testing

Sabre® makes two test partitions available to Developers.  Those test partitions, known as "TSTS" and "CERT,"  exist
separately from the production environment, known as "RES."  They do not interact directly with production data or
each other and do not communicate with live external systems.  Some host responses are replicated, and testing
that involves interaction with test systems external to Sabre may require specific configurations to be made prior to
testing.  Developers are encouraged to consult their account management team for more details.  Access to the test
systems is automatic and assumed and does not typically require advance notification or activation
by Sabre employees on behalf of an account.

TSTS

The TSTS Test Host is an environment where code can be tested in a full-blown replica of Sabre host production
systems.  Both new code and changes to existing code in the host are tested first here.  Issues related to latency and
unexpected responses may be occasionally encountered due to the number of new programs being tested at any one
time, as well as the reduced processing power available in any test system.  When new functionality is being
introduced to the host, it will be available to developers in TSTS first.  Data in TSTS is captured from the production
host every 6-8 weeks--excluding Passenger Name Record, profile, and other personally identifiable information.  This
data is used to re-create (refresh) the TSTS host in a similar interval.  During the re-create process, data in the test
host (including possible setting changes and test scenarios created by developers prior to the re-create date) is
replaced/overlaid with new data collected on the Production Capture date.  The schedule for the recreate process is
shown below.

CERT

The CERT Test Host is a separate test partition into which programming is placed 7-10 days prior to its promotion to
full production systems (RES).  Developers are encouraged to test all existing functionality in CERT due to its
superior stability relative to TSTS.  Note, however, that there may be instances where testing and development in
TSTS is unavoidable because new functionality is not promoted to CERT until 7-10 days prior to deployment to
production.  Data in CERT is captured from the production host every 6-8 weeks--excluding Passenger Name Record,
profile, and other personally identifiable information..  This data is used to re-create (refresh) the CERT host in a
similar interval, slightly staggered from the TSTS re-create.  During the re-create process, data in the test host
(including possible settings changes and test scenarios created by developers prior to the re-create date) is
replaced/overlaid with new data collected on the Production Capture date. The schedule for the recreate process is
shown below. 

RES

RES is the shorthand name for the production reservations environment.  Testing in the production environment is
discouraged if at all possible, not only due to the costs involved, but also because of the impact to supplier inventory
and booking systems.  Developers are advised to notify and seek the advice of their Sabre Account Management
team in advance if testing in RES is to be undertaken.