Confirmed users
88
edits
QA/Automation/Projects/MTBF: Difference between revisions
Jump to navigation
Jump to search
QA/Automation/Projects/MTBF (view source)
Revision as of 09:52, 10 September 2014
, 10 September 2014no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
Mean time between failures (MTBF) is the predicted elapsed time between inherent failures of a system during operation. MTBF can be calculated as the arithmetic mean (average) time between failures of a system. The MTBF is typically part of a model that assumes the failed system is immediately repaired (mean time to repair, or MTTR), as a part of a renewal process. This is in contrast to the mean time to failure (MTTF), which measures average time to failures with the modeling assumption that the failed system is not repaired (infinite repair time). | Mean time between failures (MTBF) is the predicted elapsed time between inherent failures of a system during operation. MTBF can be calculated as the arithmetic mean (average) time between failures of a system. The MTBF is typically part of a model that assumes the failed system is immediately repaired (mean time to repair, or MTTR), as a part of a renewal process. This is in contrast to the mean time to failure (MTTF), which measures average time to failures with the modeling assumption that the failed system is not repaired (infinite repair time). | ||
[[File:Mtbf.png|frameless]] | |||
Assuming T(i) is ith running time between two failures, MTBF will be sum(T(n))/n | |||
{| style="width: 90%; margin: 0 0 1em 1em" | | {| style="width: 90%; margin: 0 0 1em 1em" | | ||
| Line 24: | Line 26: | ||
| https://github.com/Mozilla-TWQA/MTBF-Driver/ | | https://github.com/Mozilla-TWQA/MTBF-Driver/ | ||
|} | |} | ||
== Pass Criteria == | |||
Currently we set 100 hours as our pass criteria. Crash, hang are regarded as failure. | |||