Please enable JavaScript.
Coggle requires JavaScript to display documents.
Testing "Logbook number report enhancements" Sprint 12
11-4…
Testing "Logbook number report enhancements" Sprint 12
11-4-2017, Roy ten Have
-
Advice
All enhancements function as intended; all testcases executed with a positive result, no open bugs.
Risks
-
The risk of not showing a "Log and Closed" fault, therefore not showing a complete image of logged logbook entries in Maintenix
-
Obstructions
Test environments used to test the report may show a larger number of 'undertermined logbook numbers' in the report. While this is not an obstruction in testing the report's functionality, it is a good thing to know when discussing 'holes in the report' with end users. (i.e. the difference between "the report shows what it needs to show" versus "as an end user, I want to see that every logbook number has been captured correctly)
Scenario's
:check: S03 - Running the report with filter 'AML' shows all AML determined logbook numbers, and all faults + open tasks without a determined logbook number
:check: S04 - Running the report with filter 'AML' shows all AML determined logbook numbers, and all faults + open tasks without a determined logbook number
-
-
Zoom Out
The first iteration of the Logbook Number Report has been in production of some time, and a number of improvements have been identified. In Sprint 12, the following improvements are to be delivered:
- Faults logged 'against a tail' using the Log&Close function also need to appear in the report.
- When starting the report with parameter 'AML' or 'NML', the report needs to show either entries where the AML/NML is determined as well as entries where it has not been determined.