OTST_TS_OB_BOOK_01 : Generic Booking display and validation scenario

[TOP-PHE]

Description

The scenario will book an offer reusing the content of OTST_TS_OB_OFER_01 .

Note

Should we put soe logic to provide inputs allowing to select an offer with some specific criterias in the long list of offers ?
For example if I want to test a refund for a semi flexible procduct I must secure that in the list of offer proposed I am selected a semi flexible one.
Another use case would be , I want to use the offer linked with my reduction card , etc...
Etc.....

The booked offer will be displayed

Note

What are the relevant information to be displayed in the report ?

Consistency booking validation checks will be done.

Note

First check as for all scenarios is to check the response and if positive what need to be tested ?

SFR

SSD: TBD

[TOP-PHE]

2 options
1 scenario generic taking the 1st offer by default, and another scenario using parameters to customised the offer to sele
Or 1 generic scenario supporting boith

Parameters to select the offer could be wide from felvxibility, direct route, with connections, type of offer admin, ancillaries, reservation....To be defined.

We implemente the capability to add new parameters, but restrict to a minimum set in the first delivery.

[TOP-PHE]

1. We should add in the validation the check of the price as potentially the provider can chang it and in this case, he should send a warning on what was changed... Check in Friday group what code should be used.
2. Need to check other changes than price are authorised at preboooking time.
3. The following list of parameters must be checked
   Passenger = check the passenger information is equivalent to the one provided in the request. like external ref, type , age,
4. Reservation: 4 potential uses cases
   IRT
   NRT
   TLT
   NRT with mandatory reservation

and on top, currently there are 2 flow to book an IRT

1. The seat selection is done befor he pre booking
2. The seat is reserved on aa default seat at pre booking and the used can selected a dedicated one afterwards...

Due tio the level of complexity, it is recommened to focuss on NRT first deliver the scenario and increase the coverage in a second step.
Also, the team recommend to add in the list of One Business function One business logic breaking rule the IRT seat reservation flow , with bicycle (ancillary or PAX) and Supplement (fee or supplement ?)