Guidance for Schema Version:
Definition of Capability
Negative test cases (e.g. triggering and testing involuntary scenarios)
NOTE: System Providers will use the above definition that pertains to their customers for Capabilities Verification.
Links to EASD Implementation Guidance
NOTE: Retailing Capabilities Verification Guidance will align to the published EASD Implementation Guidance at all times. From time to time when new guidance is published this will be updated and supersede any Retailing Capabilities Verification Guidance listed below.
Retailing Capabilities Verification Guidance
Provide link to online documentation or screenshots of test environment documentation demonstrating support for negative test cases, for example:
Triggering “involuntary” scenarios, e.g. flight disruptions and schedule changes.
Simulating different types of payment failures and asynchronous payment status updates.
Entering criteria / parameters into shopping queries that are incorrect or not supported by the Airline.
Attempts at servicing an Order in ways that may conflict with Airline’s internal business logic.
NOTE: For all versions prior to that listed above (generally the most recent), the verification will be based on the guidance available for that version. In the case that no guidance is available, verification will be at IATA’s discretion.