Firefox OS/Performance/MTBF: Difference between revisions
< Firefox OS | Performance
Jump to navigation
Jump to search
Bobbychien (talk | contribs) (→Team: update name) |
Bobbychien (talk | contribs) (Update) |
||
| Line 9: | Line 9: | ||
|- | |- | ||
|} | |} | ||
== MTBF Dashboard == | |||
* [https://groups.google.com/a/mozilla.com/forum/#!forum/fxos-mtbf MTBF Mailing Group] | |||
* [https://raptor.mozilla.org/dashboard/script/mtbf?var-device=flame-kk&var-memory=512&var-branch=master Flame 512MB] | |||
* [https://raptor.mozilla.org/dashboard/script/mtbf?var-device=aries&var-memory=2048&var-branch=master&var-node=mtbf-3 Aries 2GB] | |||
=== Test Methodology === | |||
* [https://wiki.mozilla.org/QA/Automation/Projects/MTBF QA Automation MTBF] | |||
=== 2015 Q4 Plan === | === 2015 Q4 Plan === | ||
* Adopt stress test for MTBF testing | * Adopt stress test for MTBF testing | ||
* Integrate MTBF tests to Raptor test framework | * Integrate MTBF tests to Raptor test framework | ||
* Improve current MTBF tests (simulate user behavior) to stress/heavy tests | |||
=== 2015 Q3 Plan === | === 2015 Q3 Plan (Done) === | ||
* Plan to start new test methodology. | * Plan to start new test methodology. | ||
** Daily MTBF tests, max result is 24 hours. | ** Daily MTBF tests, max result is 24 hours. | ||
** Weekly (Long term) MTBF test, max result is average of tested device when full terminated | ** Weekly (Long term) MTBF test, max result is average of tested device when full terminated | ||
=== 2015 Q2 Plan (Done) === | === 2015 Q2 Plan (Done) === | ||
* [Done] Daily MTBF automation test and report sent by email | * [Done] Daily MTBF automation test and report sent by email | ||
=== [https://bugzilla.mozilla.org/show_bug.cgi?id=1034485 Working Items] === | === [https://bugzilla.mozilla.org/show_bug.cgi?id=1034485 Working Items] === | ||
| Line 33: | Line 40: | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
Latest revision as of 04:05, 27 October 2015
Team
| Raptor Dashboard | http://raptor.mozilla.org/#/dashboard/file/raptor.json |
| Program Management | Bobby Chien |
| QA (Taipei) | Paul Yang, Shako Ho |
MTBF Dashboard
Test Methodology
2015 Q4 Plan
- Adopt stress test for MTBF testing
- Integrate MTBF tests to Raptor test framework
- Improve current MTBF tests (simulate user behavior) to stress/heavy tests
2015 Q3 Plan (Done)
- Plan to start new test methodology.
- Daily MTBF tests, max result is 24 hours.
- Weekly (Long term) MTBF test, max result is average of tested device when full terminated
2015 Q2 Plan (Done)
- [Done] Daily MTBF automation test and report sent by email
Working Items
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);