FirefoxOS/DeviceQA/2015-03-16WeeklyReport: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(MikeLien weekly report)
No edit summary
Line 24: Line 24:
||
||
* Week W12 (03/16~03/20)
* Week W12 (03/16~03/20)
 
** Bugs verify
** Monitor Nexus-5-L MTBF testing
** NFC workweek remote sessions
||
||
* Week W13 (03/23~03/27)
* Week W13 (03/23~03/27)
 
** Bugs verify
** Monitor Nexus-5-L MTBF testing
|-
|-
|Askeing
|Askeing

Revision as of 03:19, 26 March 2015

Last week | Next week

Name Done Plan
Al
  • Week W12 (03/16~03/20)
    • MCTS v2.2
    • Bug 1116878 - [2.1] Most bluetooth tests fail with "app = null" error
      • attempting to resolve it again \_/#
    • Have a release for MCTS v2.2 in this week
    • Marionette Issue
    • Support Fire2-3.5 MCTS
  • Week W13 (03/23~03/27)
    • Have a release for MCTS v2.2 in this week
Alison
  • Week W12 (03/16~03/20)
    • Bugs verify
    • Monitor Nexus-5-L MTBF testing
    • NFC workweek remote sessions
  • Week W13 (03/23~03/27)
    • Bugs verify
    • Monitor Nexus-5-L MTBF testing
Askeing
  • Week W12 (03/16~03/20)
    • MCTS issues fixing.
    • Bug 1142421 - marionette-extension should support v2.2
    • Bug 1142422 - fxosapp-gen should support v2.2 officially
    • Bug 1143531 - [MCTS] update the dependencies to support v2.2
    • Bug 1144605 - NameError: global name 'dm' is not defined
    • Bug 1142430 - [MCTS] The semiauto tests will show "Could not close CertTest App automatically..." error message.
    • Bug 1144536 - [MCTS] Change omni.ja test with a proper presentation in report
  • Week W13 (03/23~03/27)
    • MCTS issues fixing.
    • Investigate the log/report of MCTS
    • Bug 1144536 - [MCTS] Change omni.ja test with a proper presentation in report
    • Investigate the python diff mechanism for checking omni.ja
Cynthia
  • Week W12 (03/16~03/20)
  • Week W13 (03/23~03/27)
Edward
  • Week W12 (03/16~03/20)
  • Week W13 (03/23~03/27)
Eric
  • Week W12 (03/16~03/20)
    • Check for v2.2 bug status
  • Week W13 (03/23~03/27)
    • Check for v2.2 bug status
    • Check resource for Marigold
Gerry
  • Week W12 (03/16~03/20)
    • v2.2 feature testing
      • Privacy Controls feature - keep testing.
      • Follow up unresolved issues.
    • QAnalyst/MGSEI bugs verification/follow-up
    • Nexus 5 automation test monitoring
    • Test Spec template drafting
  • Week W13 (03/23~03/27)
    • v2.2 feature testing
      • Privacy Controls feature - keep testing.
      • Follow up unresolved issues.
    • QAnalyst/MGSEI bugs verification/follow-up
    • Nexus 5 smoke test result verification
    • Test Spec template drafting
Hermes
  • Week W12 (03/16~03/20)
    • Monitor v2.2+ System FE Bugs
      • Feature landing verification of Bug 1001861
      • Monitor SysFE bugs
    • Start MozTrap enhancement
      • Study react.js
      • implement a feature
  • Week W13 (03/23~03/27)
    • Monitor v2.2+ System FE Bugs
      • Monitor SysFE bugs for FL milestone
    • Refine 2.2 CI script
    • MozTrap enhancement project
      • implement features if time is enough
Hubert
  • Week W12 (03/16~03/20)
    • Follow up Woodduck tasks and issues
    • Outsourcing weekly meeting
    • Bug work for Marigold submitted bugs
    • Modify and create test cases for In-House FOTA (Completed: 85%)
    • In-House FOTA testing strategy discussion with PM and RD.
    • Generate lesson learn document for woodduck project. (Completed: 80%)
    • Study OTA data migration automation test
  • Week W13 (03/23~03/27)
    • Follow up Woodduck tasks and issues
    • Outsourcing weekly meeting
    • Bug work for Marigold submitted bugs
    • Modify and create test cases for In-House FOTA
    • In-House FOTA testing strategy discussion with PM and RD.
    • Generate lesson learn document for woodduck project.
    • Study OTA data migration automation test
    • Review and modify SOW document for QA outsourcing
Mike
  • Week W12 (03/16~03/20)
    • v2.1 bug work
    • Power consumption measurement
    • Support Madai issue verification
    • New SUPL server follow up
  • Week W13 (03/23~03/27)
    • v2.1&v2.1s bug work
    • Power consumption measurement
    • Woodduck A-GPS verification
Owen Ouyang
  • Week W12 (03/16~03/20)
  • Week W13 (03/23~03/27)
Paul
  • Week W12 (03/16~03/20)
  • Week W13 (03/23~03/27)
Shing
  • Week W12 (03/16~03/20)
    • New test case management system prototyping
    • Metrics testing + test case update
    • MozTrap enhancements
      • Meetings with US team + qanalyist
      • Meetings with Johan
  • Week W13 (03/23~03/27)
    • Test case management system prototyping
    • Metrics Testing
    • MozTrap enhancements retrospect
    • Prepare sharings on MozTrap enhancement
    • Interview RDs on their automation testing practices
Teri
  • Week W12 (03/16~03/20)
  • Week W13 (03/23~03/27)
Walter
  • Week W12 (03/16~03/20)
  • Week W13 (03/23~03/27)
William Hsu
  • Week W12 (03/16~03/20)
    • [Device]
      • Bug work
      • GU test on Flame v2.0 & Flame v2.1 & Dolphin v2.1s
    • [Outsourcing]
      • RTL test case review
      • Dispatch bugs of free test
      • Q1 performance review and documentations
  • Week W13 (03/23~03/27)
    • Marriage leave, 3/23~3/27
Shako Ho
  • Week W12 (03/16~03/20)
    • minor fix patch for MTBF
      • makefile added for mtbf-driver
      • makefile modification for mtbf-operation
    • add auto generated report for MTBF job in jenkins
  • Week W13 (03/23~03/27)
    • add mtbf operation daily task in jenkins
Retrieved from "https://wiki.mozilla.org/index.php?title=FirefoxOS/DeviceQA/2015-03-16WeeklyReport&oldid=1064556"