Transcript Test Planning 2/28/05 (ppt)

GLAST LAT Project
Agenda for Feb 28, 2005
•
•
Strategy for test failures caused by known hardware issues
– We have some known Cal and Tracker hardware that does not
perform as expected
• CAL FM 107 has extra noise on a log end
• Tracker has channels that are out and channels that are
partially disconnected
– The “standard” approach would be to run the test, note that it
failed, then verify that the failure matched currently documented
failures
– Discussion on an automated way to do this
• Cal has defined an exception list for specific tests, and allow a
pass even when items on the exception list fail
• This could be extended to other items (Tracker is currently
working on a similar approach)
• Any drawbacks to using this approach?
• Should there be a “conditional pass” rather than a “pass”?
First cut at the LAT level test matrix is available for review
LAT System Engineering
1