QA/B2G/How To Test Firefox OS/Power Menu
From MozillaWiki
< QA | B2G | How To Test Firefox OS
Contents
Power Menu
Stability (Open to Test)
- Link to: Developer's status
How to test this App
- Access Points
- Anywhere on the phone
- Data Management
- No data
- Areas to test
- Menu UI
- Airplane Settings
- Ring Settings
- User Actions
- Toggle Airplane Mode
- Toggle/silence incoming calls
- Restart phone
- Power off
- Positive & Negative Testing
- Positive Examples
- Power off Device
- Restart device
- Negative Examples
- Maintain state of Airplane mode after toggling
- Boundary Testing
- Race Conditions
- http://en.wikipedia.org/wiki/Race_condition
- Power off Device while receiving a phone call
- Restart device while triggering an alarm
- http://en.wikipedia.org/wiki/Race_condition
FXOS Contacts
- Team Members
- Power Menu QA Owner
- Parul Mathur
Fixed in last 7 days
Open Bugs
Last 7 days |
---|
Bugzilla query error
|
All open bugs |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
All open blockers/noms |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
Sprint Details
Design Documents
- Building Blocks
User Stories Metas
All Metas |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
Open User Stories |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
All User Stories |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
Setup
- 1. Hold down power button.
Automation Scripts
- How to Run Automation
- gaiatest --testvars=gaiatest/testvars.json --address=localhost:2828 --restart --timeout=100000 gaiatest/tests/functional/settings/test_power_button_long_press.py
- Automated Power Menu Smoketests
- No smoketests for Power Menu
- All Gaia-UI Functional Tests
- Unit Tests
- n/a
Logging
- Please provide the logcat by running adb logcat -v time -s GeckoDump:V Gecko:V GeckoConsole:V OomLogger:V | tee FILENAME-TO-LOG-TO. Please start running this command BEFORE you attempt to reproduce the problem. logcat uses a circular buffer that discards older entries when the buffer fills up, so if you run logcat only after the problem happens, you may not have all of the logic. Once you are done, hit control-C and send us the file.
Bug Writing
- Link to Bug Writing Document