Please enable JavaScript.
Coggle requires JavaScript to display documents.
Testing Mxi fix 'Mandatory Fields'
3-5-2017, Roy ten Have
Last…
Testing Mxi fix 'Mandatory Fields'
3-5-2017, Roy ten Have
Last update 4-5-2017
Test goals
:check: Validation check on "Logbook number reference" only accepts 'not populated', '8 digit number' or '8 digits + 1 alphanumeric'
-
-
-
:check: Validation checks do not hinder "COMPLETED" or "Marked as Error" faults, prior to the implementation of these checks
:red_cross: Data captured in the 'Defer fault' screen is kept/saved when a validation check message is shown, in order to minimize user input after correctly enriching the fault.
-
:check: Validation checks work with all various Fault Severities (MEL, NSRE, CDL, EXMP, TLI, AOG or Unknown)
:check: Enabling the Validation checks does not result in Maintenix sending out fault updates via the KLM custom API
:check: Enabling the Validation checks does not impact Maintenix sending out the correct messages to FIA
:check: Validations are triggered by either using the GUI or Rubritext integration (Diagnostics API)
Scenarios
-
Logbook number Reference
-
-
-
-
-
-
:check: S07 - The validation check on Logbook Number Reference is executed when editing a fault, or deferring a fault
-
-
Lifecycle of a Fault
:check: S07 - Marking a historic Fault as Error (with an 'old' logbook number i.e. M501) is possible
-
-
-
-
-
-
Zoom out
In order to ensure a greater level of data integrity, Mxi created a KLM specific patch which validates certain fields in Maintenix the moment a fault is edited or being deferred.
Risks
R02 - Risk that the given error messages are not clear enough, or are misunderstood
R01 - Risk that faults with an old (Mnnn) logbook number can no longer be 'updated' with the correct Mnnn logbook number (i.e. following procedure "TS-013 - Correcting a Mistake") as the validation check enforces the new logbook number format
R03 - All validation checks rely on the (previously turned off) KLM custom triggers, which in Maintenix 8.2 need to be again provided in the Customizations
R04 - There is a risk something will change, or not work anymore in the KLM custom triggers -- and in extension these validation checks.
Advice
Even though the 'Defer fault' page does not save previously entered deferral data (for ease of use when deferring after entering mandatory data correctly), all validations work according to design.
To mitigate R01: Mitigation is to remove the old slip number from the Logbook Reference and add it to the fault description. A procedure is provided to end users.
To mitigate R02: additional communication about the validations is to be provided to end users.
To mitigate R03: specifically test these custom validations in 8.2 as part of regression and incorporate these in the automated regression
To mitigate R04: add the validations to the manual 8.1 regression test to know if core or custom patches introduce regression
Bugs
Fields captured on the "Defer Fault" page are not saved and repopulated, after populating the mandatory fields and clicking on the 'Defer Fault' button
Error message
"Work performed hours on the Fault Execution tab must be filled in for all the labour skills on the Fault Execution tab must be filled in for all the labour skills"
is not related to the Work Performed Hours, but to the "Work Performed Sched. Hours"