Firefox OS/DeviceQA/DeviceQAWiki: Difference between revisions
< Firefox OS | DeviceQA
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
** Suggested Pass Criteria: MTBF > 100 hours | ** Suggested Pass Criteria: MTBF > 100 hours | ||
** [https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/MTBF_tests MDN: MTBF] | ** [https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/MTBF_tests MDN: MTBF] | ||
** [https://wiki.mozilla.org/QA/Automation/Projects/MTBF Wiki: MTBF] | |||
* Monkey Test | * Monkey Test | ||
** Monkey Test of Firefox OS is based on [https://github.com/mozilla-b2g/orangutan Orangutan tool]. | ** Monkey Test of Firefox OS is based on [https://github.com/mozilla-b2g/orangutan Orangutan tool]. | ||
| Line 33: | Line 34: | ||
** Endurance won't be part of our regular tests since it takes more time. You can have a look of endurance testing result of our reference phone (Flame) from [https://datazilla.mozilla.org/ datazilla]. | ** Endurance won't be part of our regular tests since it takes more time. You can have a look of endurance testing result of our reference phone (Flame) from [https://datazilla.mozilla.org/ datazilla]. | ||
** [https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/Endurance MDN: Endurance] | ** [https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/Endurance MDN: Endurance] | ||
=== Performance === | === Performance === | ||
* Performance (not maintained in Taipei) | * Performance (not maintained in Taipei) | ||
Revision as of 06:09, 17 September 2014
Note of handling device project
- Weekly report should be delivered to stakeholders.
- "fxosqa-report-watchlist" is a public mailing list, please consider if report should be delivered to them.
Manual Test
- Sanity Test
- Smoke Test (Manual/Auto)
- Acceptance Test
- CRT (Certification Requirement Test) [TBD]
- Functional Full Test
- Regression Test
- Exploratory Test
- Performance Test (Manual/Auto)
- RAT (Release Acceptance Test)
Automation
When a project kick-off, Device QA team will start to arrange following environment for testing. Partners should aware it's not required. However, we still recommend partners setup the same environment for quick responding issues found at both sides. We also suggest to discuss about which testing you'd like to have and their pass criteria with TAM before a project kick-off.
Functionality
- Gaia-UI-Test
- gaia-ui-tests cover functionality testing by checking and interacting with HTML elements rendered on screen. Device QA team suggests to execute on real devices.
- Suggested Pass Criteria: All green for five days
- MDN: Gaia-ui-test
Stability
- MTBF (Mean Time Between Failures)
- MTBF is often used for measuring stability. Failures mentioned here include crashes and hang.
- Suggested Pass Criteria: MTBF > 100 hours
- MDN: MTBF
- Wiki: MTBF
- Monkey Test
- Monkey Test of Firefox OS is based on Orangutan tool.
- Suggested Pass Criteria: No crashed > 100 hours
- Github: Monkey Test
- Endurance Test (not maintained in Taipei)
- Endurance won't be part of our regular tests since it takes more time. You can have a look of endurance testing result of our reference phone (Flame) from datazilla.
- MDN: Endurance
Performance
- Performance (not maintained in Taipei)
- You can have a look of performance result of our reference phone (Flame) from datazilla
- MDN: Gaia UI Performance
Certification
- MCTS (Mozilla Certificate Test Suite)