QA/B2G/How To Test Firefox OS/Usage

From MozillaWiki
Jump to: navigation, search

Usage

Stability (Open to Test)

Link to: Developer's status

How to test this App

Link to: One and Done Items
Usage Application Coverage
Access Points
  • Homescreen
  • Notification Tray
Data Management
  • Data Usage
  • Wifi Usage
  • Report Reset date
  • Usage Alerts
Areas to test
  • Usage FTU
  • Usage Main View
  • Usage Settings
  • INdividual App View
  • Notification tray access
User Actions
  • Enabling/Disabling Mobile and WIFI Usage
  • Enable/Disable Data Use Alert
  • Set Report Reset dates
Positive & Negative Testing
http://www.guru99.com/positive-vs-negative-testing.html
Positive Examples
  • Test with WiFi on and view WiFi Usage
  • Change Report reset date
Negative Examples
  • Trying to Track 2 SIMs through 1 Usage plan
Boundary Testing
http://en.wikipedia.org/wiki/Boundary_testing
  • Test with a Data alert at 999GB
  • Test with Data Alert at 1MB
Race Conditions
http://en.wikipedia.org/wiki/Race_condition
  • Begin Usage FTU and before finishing, change SIM 2 to be primary

FXOS Contacts

Team Members
Usage QA Owner
  • Shing Lyu

Fixed in last 7 days

Open Bugs

Last 7 days

Bugzilla query error

Sprint Details

Design Documents

UX Specs
https://mozilla.app.box.com/applications
Building Blocks
https://wiki.mozilla.org/Gaia/Design/BuildingBlocks
https://etherpad.mozilla.org/b2g-features-checklist

User Stories Metas

Setup

1. Navigate throught the Usage FTU

Automation Scripts

How to Run Automation
gaiatest --testvars=gaiatest/testvars.json --address=localhost:2828 --restart --timeout=100000 gaiatest/tests/functional/cost_control/manifest.ini
Automated Cost Control Smoketests
  • test_cost_control_data_alert_mobile.py
All Gaia-UI Functional Tests
https://github.com/mozilla-b2g/gaia/tree/master/tests/python/gaia-ui-tests/gaiatest/tests/functional/cost_control
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