UAT Validation

Go-live validation steps, templates, evidence, and submission path.

Use this page when your sandbox integration is ready for go-live validation.

Goal of this phase

Validate that the sandbox integration is ready for production.

This phase converts a completed sandbox integration into an approved go-live result.

When to start UAT

Start UAT after:

• sandbox credentials are working

• the core booking flow is integrated

• request headers and authentication are stable

• webhook handling is ready if full integration UAT is required

• your team can execute test cases end to end

UAT tracks

There are two UAT tracks.

1. Shopping and Ticketing UAT

Use this track when you need to validate the standard search-to-ticket flow.

This usually covers:

• search

• verify

• order

• payment

• ticketing result

2. Full Integration UAT

Use this track when you need to validate the end-to-end integration between Atlas and your booking platform.

This usually covers:

• passenger type combinations

• trip type combinations

• direct and connecting itineraries

• payment methods

• ancillaries

• webhooks

• operational follow-up flows

What to prepare before submission

Prepare these items before submitting UAT:

• completed UAT template

• test evidence for each scenario

• expected and actual results

• relevant order numbers or request IDs

• webhook evidence when full integration is tested

• the Postman collection used by your team, if needed

Recommended execution order

1

Download the correct template

Pick the UAT track that matches your integration scope.

2

Run all required scenarios

Execute every scenario in sandbox and record the result clearly.

3

Attach evidence

Include request outcomes, screenshots, webhook samples, and order references where relevant.

4

Submit via ATRIP

Submit the completed UAT result through Eva in ATRIP.

5

Wait for review feedback

Atlas reviews the submission and may request clarification or retesting.

Download resources

Shopping and Ticketing UAT template

189KB

Atlas UAT Test Shopping & Ticketing Services Only Template.xlsx

Open

Shopping and Ticketing Postman collection

5KB

Atlas UAT Test Shopping & Ticketing Services Only Postman Collection.zip

archive

Open

Full Integration UAT template

11KB

Atlas UAT Test Full Integration Template.xlsx

Open

Full Integration Postman collection

3KB

Atlas UAT Test Full Integration Postman Collection 20230424.zip

archive

Open

Submission path

After you complete the relevant template, submit the results through Eva in ATRIP.

==>

Common reasons a submission is sent back

• missing scenarios

• incomplete expected or actual results

• no supporting evidence

• unclear passenger or trip type coverage

• webhook flow not demonstrated for full integration UAT

Complete this phase when

You have all of these:

• submitted the correct UAT track

• attached the required evidence

• resolved any review feedback

• received UAT approval

Output of this phase

• approved UAT result

• confirmed go-live readiness

Next step

After UAT passes:

• ask your customer manager to switch the account to LIVE

• generate production credentials

• set up the production IP whitelist

• replace sandbox endpoints

• run a controlled smoke test

• monitor the first live orders and webhook events

Related pages

• Sandbox Development

• Quick Start

• Production Go-Live

• Webhook Overview