Test Paramets

  • Hotel: ${hotelId}
  • Room Type1: ${roomId1}
  • Room Type2: ${roomId2}
  • Rate Plan1: ${rateId1}
  • Rate Plan2: ${rateId2}
  • Checkin: ${checkin}
  • Checkout: ${checkout}
  • Start Date: ${startDate}
  • End Date: ${endDate}


No.Category
Test Scenario
Test Objective
Expected Result
EchoTokens

1

Property

Create ${hotelId}

Verify if the Property Update works well

  1. The format of request message follows the spec

  2. The property status sends as Bookable

2

Content

Create ${roomId1} and ${roomId2} for ${hotelId}

Verify if the Room Creation works well

  1. The format of request message follows the spec

  2. The room status sends as Actived

3

Content

Create ${rateId1} and ${rateId2} for ${hotelId}

Verify if the Rate Plan Creation works well

  1. The format of request message follows the spec

  2. The rate plan status sends as Actived

4

Content

Create ${rateId1} assigned with ${roomId1} and ${roomId2}, ${rateId2} assigned with ${roomId1} and ${roomId2} for ${hotelId}

Verify if Products Creation work well

  1. The format of request message follows the spec

  2. The product status sends as Actived

5

ARI

Full refresh by ${hotelId} with date range from ${startDate} to ${endDate}

Verify if the full refresh works well on:

  1. Update Rate

  2. Update Inventory

  3. Update Availability

  1. The pushing messages are indicator with Overlay

  2. The data are completed in the date range

  3. The format of request message follows the spec

6

ARI

Manual full refresh by ${hotelId} with date range from ${startDate} to ${endDate}

Verify the manual full refresh messages are same with case#1

The messages are same with case#1

7

Reservation

Make a successful single room reservation for ${hotelId} on ${checkin} with 1 night and 2 adults on ${roomId1} and ${rateId1}

Verify if the reservation can be processed well by your PMS

  1. HTTP status code with 200 from your PMS

  2. The format of response message follows the spec 

  3. supplierResId is included in the response

8

Reservation

Cancel the reservation of case#3

Verify if the reservation can be cancelled

  1. HTTP status code with 200 from your PMS

  2. The format of response message follows the spec

  3. cancellationId is included in the response

9

Reservation

Make a successful 3 rooms reservation for ${hotelId} on ${checkin} with 1 night and 2 adults on ${roomId1} and ${rateId1}

Verify if multiple reservations can be processed well by your PMS

  1. All 3 reservations can be booked to your PMS and get successful response for each ones.

  2. Three different supplierResId returned back from your PMS

10

Reservation

Cancel the reservation of case#5

Verify if the splitting reservations can be cancelled

  1. All 3 bookings in the PMS succesfully cancelled

  2. Three different cancellationId returned back from your PMS

11

ARI

Close only on ${roomId1} and ${rateId1} for ${checkin}

Verify if close message can be pushed out

  1. The pushing messages are indicator with Delta

  2. The format of request message follows the spec

  3. Only ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and masterClose is true

12

Reservation

Make a fail reservation to the closed products of ${roomId1}, ${rateId1} on ${checkin} in Booking Request model

Verify if the reservation will be rejected by PMS

  1. HTTP status code with 500 from your PMS

  2. The format of response message follows the spec

  3. errorCode and errorMesage are included in the response

13

Reservation

Make a successful reservation to the closed products of ${roomId1}, ${rateId1} on ${checkin} in Booking Notify model

Verify if the reservation will be accept by PMS

  1. HTTP status code with 200 from your PMS

  2. The format of response message follows the spec 

  3. supplierResId is included in the response

14

ARI

Open only on ${roomId1} and ${rateId1} for ${checkin}

Verify if open message can be pushed out

  1. The pushing messages are indicator with Delta

  2. The format of request message follows the spec

  3. Only ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and masterClose is false

15

ARI

Change only the rate of ${roomId1} and ${rateId1} for ${checkin} to 100

Verify rate changes

  1. The pushing messages are indicator with Delta

  2. The format of request message follows the spec

  3. Only ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and rates is 100

16

ARI

Change only the inventory of ${roomId1} and ${rateId1} for ${checkin} to 10

Verify inventoy changes

  1. The pushing messages are indicator with Delta

  2. The format of request message follows the spec

  3. Only ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and inventory is 10

17

ARI

Change only the minStayThrough of ${roomId1} and ${rateId1} for ${checkin} to 2

Verify availability changes

  1. The pushing messages are indicator with Delta

  2. The format of request message follows the spec

  3. Only ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and minStayThrough is 2

18

ARI

Change only the maxStayArrival of ${roomId1} and ${rateId1} for ${checkin} to 2

Verify availability changes

  1. The pushing messages are indicator with Delta

  2. The format of request message follows the spec

  3. Only ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and maxStayArrival is 2

19

ARI

Change only the minAdvanceDay of ${roomId1} and ${rateId1} for ${checkin} to 2

Verify availability changes

  1. The pushing messages are indicator with Delta

  2. The format of request message follows the spec

  3. Only ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and minAdvanceDay is 2

20

ARI

Change only the maxAdvanceDay of ${roomId1} and ${rateId1} for ${checkin} to 2

Verify availability changes

  1. The pushing messages are indicator with Delta

  2. The format of request message follows the spec

  3. Only ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and maxAdvanceDay is 2

21

ARI

Manual full refresh by ${hotelId} with date range from ${startDate} to ${startDate}

Verify full refresh

  1. The pushing messages are indicator with Overlay

  2. The format of request message follows the spec

  3. ${roomId1} and ${rateId1} with ${checkin} is inclued in the request and
    inventory is 10
    minStayThrough is 2
    maxStayArrival is 2
    minAdvanceDay is 2
    maxAdvanceDay is 2

22

Reservation

Make a successful single room reservation for ${hotelId} on ${checkin} with 1 night and 2 adults on ${roomId1} and ${rateId1}, ${checkin} is equal to booked date

Verify if the reservation can be processed well by your PMS

  1. HTTP status code with 200 from your PMS

  2. The format of response message follows the spec 

  3. supplierResId is included in the response

23

Reservation

Change the reservation status to check-in of case#22 

Verify if the reservation status changes

  1. The format of request message follows the spec

  2.  The reservation status sends as Inhouse

24

Reservation

Change the reservation status to check-out of case#22

Verify if the reservation status changes

  1. The format of request message follows the spec

  2.  The reservation status sends as CheckedOut

25

Reservation

Make a successful single room reservation for ${hotelId} on ${checkin} with 1 night and 2 adults on ${roomId1} and ${rateId1}, ${checkin} is equal to booked date

Verify if the reservation can be processed well by your PMS

  1. HTTP status code with 200 from your PMS

  2. The format of response message follows the spec 

  3. supplierResId is included in the response

26

Reservation

Change the reservation status to cancel of case#25 

Verify if the reservation status changes

  1. The format of request message follows the spec

  2.  The reservation status sends as Cancelled

  3. cancellationId is included in the response

  4. cancellationDate is included in the response

27

Reservation

Make a successful single room reservation for ${hotelId} on ${checkin} with 1 night and 2 adults on ${roomId1} and ${rateId1}, ${checkin} is equal to booked date

Verify if the reservation can be processed well by your PMS

  1. HTTP status code with 200 from your PMS

  2. The format of response message follows the spec 

  3. supplierResId is included in the response

28

Reservation

Change the reservation status to NoShow of case#27 (after night audit)

Verify if the reservation status changes

  1. The format of request message follows the spec

  2.  The reservation status sends as NoShow