Testing Mxi fix 'Mandatory Fields'
3-5-2017, Roy ten Have
Last update 4-5-2017

Test goals

✅ Validation check on "Logbook number reference" only accepts 'not populated', '8 digit number' or '8 digits + 1 alphanumeric'

✅ Validation check on "Estimated Duration" only accepts values above 0:00

✅ Validation check on "Work Type" only accepts values other than 'empty'

✅ Field checks are performed when a fault is deferred

✅ Validation checks do not hinder "COMPLETED" or "Marked as Error" faults, prior to the implementation of these checks

Scenarios

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

❌ 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.

✅ Validation checks work in conjuncture with eachother

Advice

Bugs

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



Fields captured on the "Defer Fault" page are not saved and repopulated, after populating the mandatory fields and clicking on the 'Defer Fault' button


Multiple validation errors

Logbook number Reference

✅ S01 - Fault is deferred when all the following errors are present:

  • Logbook Reference does not contain a valid entry
  • Estimated Duration does not contain a valid entry
  • Work Type does not contain a valid entry

And the correct error messages show when deferring the fault

✅S02 - Exactly 8 digits is accepted

✅ S03 - More than 8 digits is not accepted

✅ S01 - Less than 8 digits is not accepted

✅ S04 - 8 digits and 1 letter is accepted

✅ S05 - 8 Digits more than 1 letter is not accepted

✅ S06 - 8 Digits and a character other than a letter is not accepted

✅ S02 - Fault is deferred when two of the following is true:

  • Logbook Reference does not contain a valid entry
  • Estimated Duration does not contain a valid entry
  • Work Type does not contain a valid entry

And the correct error messages show when deferring the fault

✅ S03 - Fault is deferred when only one of the following is true:

  • Logbook Reference does not contain a valid entry
  • Estimated Duration does not contain a valid entry
  • Work Type does not contain a valid entry

And the correct error message show when deferring the fault

Estimated Duration

✅ S01 - Estimated Duration 0:00 is not accepted

✅ S02 - Estimated Duration other than 0:00 is accepted

✅ S03 - Updating the Estimated Duration from a valid value to 0:00 is not accepted

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"


Work Type

✅ S02 - Choosing any Work Type is accepted

✅ S03 - Updating the Work Type to 'empty' is not accepted

✅ S01 - Not choosing a Work Type is not accepted

R02 - Risk that the given error messages are not clear enough, or are misunderstood

✅ S07 - The validation check on Logbook Number Reference is executed when editing a fault, or deferring a fault

Lifecycle of a Fault

✅ S07 - Marking a historic Fault as Error (with an 'old' logbook number i.e. M501) is possible

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

✅ Validation checks work with all various Fault Severities (MEL, NSRE, CDL, EXMP, TLI, AOG or Unknown)

✅ Enabling the Validation checks does not result in Maintenix sending out fault updates via the KLM custom API

✅ Enabling the Validation checks does not impact Maintenix sending out the correct messages to FIA

✅ Validations are triggered by either using the GUI or Rubritext integration (Diagnostics API)

✅ S01 - Creating a Fault via ACARS/Rubritext triggers the validation checks

✅ S02 - Creating a Fault via the GUI triggers the validation checks

✅ S03 - (Un)Assigning faults to Work Packages does not trigger the validation checks

✅ S04 - Job Stop of a labor row does not trigger the validation checks

✅ S05 - Finishing of a labor row does not trigger the validation checks

✅ S06 - Completing a Work Package does not trigger the validation checks

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.