Please enable JavaScript.
Coggle requires JavaScript to display documents.
TESTING
"As a TS I want to see flight information in a fault created…
TESTING
"As a TS I want to see flight information in a fault created through ACARS"
8-6-2017, Roy ten Have
Tested on UTE / AE3 - 19-6-2017
Tested on UTE / AE1 - 21-06-2017
Advice
Positive
- All testcases executed with a 'passed' result
- No open bugs
Bugs
-
:check: FIXED Telex text shows line feed code, instead of showing parts of the telex on new lines in the Maintenix 'description' field.
Risks
Accepted Risk by Product Owner
This solution matches the date/time of the ACARS message with the date/time of the scheduled flight. In situations where the flight is delayed, it is therefore possible no Flight can be 'found' (matched) in Maintenix - depending on the moment the fault is sent via ACARS.
Test goals
:check: ACARS faults are automatically enriched with the 'Found on Flight' data in Maintenix - in case that an ACARS fault is sent between the "Scheduled Departure" and "Scheduled Arrival" of said flight.
:check: In case a flight cannot be found (i.e. due to a flight delay), the ACARS message will be enriched with a text stating this.
:check: If it takes too long for Maintenix to find a matching Flight, the ACARS message will be sent without one - in this case it will be enriched with a text stating this,
-
Scenarios
-
-
Negative flow & Failover
:check: During Request-Response of the Flight number, Maintenix does not reply at all -- Fault will not be enriched with a Flight number, and will be enriched with text "<no response from Mx....?>"
:check: During Request-Response of the Flight number, Maintenix replies with an error message -- Fault will not be enriched with a Flight number, and will be enriched with text "<no response from Mx....?>"
:check: During Request-Response of the Flight number, Maintenix replies after the wait time for the response -- Fault will not be enriched with a Flight number, and will be enriched with text "<no response from Mx....?>"**
Zoom out
TS would like faults created with ACARS to contain the Flight number on which the fault was found, so as to reduce manual entry.
A solution was devised in which for every ACARS message sent, the middleware queries Maintenix using the xxx message to retrieve the Flight number.
This solution matches the time from which a fault via ACARS is sent down to the scheduled time of a flight in order to enrich the message with the Flight ID. This means that any ACARS message is sent after the scheduled arrival time (in case of delays), will not find a matching Flight ID.