FirefoxOS/DeviceQA/2015TestRoadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Start this page)
 
 
(6 intermediate revisions by one other user not shown)
Line 7: Line 7:
**Al, Askeing, Owen, Cynthia
**Al, Askeing, Owen, Cynthia
*Stability
*Stability
**Paul, Walter, Shoko
**Paul, Walter, Shako


==2015 Short term==
==2015 Short-term==
*OS Support
OS Support
**2.2 release
*2.2 release
***Milestone criteria gatekeeper
**Milestone criteria gatekeeper
***Provide project health status
**Provide project health status
***Balance resource load
**Balance resource load
***Increase automation rate
**Increase automation rate
***Test case review meeting
**Test case review meeting
***Module ownership
**Module ownership
**3.0
**Regular Performance report
***Gaia UI test in JavaScript or follow the automation members’ (Geo, Johan) plan
***work with EPM to come out the performance scenarios and criteria
***Prepare for 3.0
*2.5
**Gaia UI test in JavaScript or follow the automation members’ (Geo, Johan) plan
**Prepare for 2.5
 
Device branch
*2.0M Woodduck
*2.1S Dolphin
*2.2 new devices branch
*other devices support
*Work with 3rd party test lab
*Device release process
*Health status
 
MCTS
*2.0, 2.1 release package support and maintenance
*2.2 new architecture design and package delivery
**2015/06 ship the first package
*easy to install, execute and troubleshooting
*web site must be up to date
**http://fxos-certsuite.readthedocs.org/en/latest/
*work with partners to have the clear process and help on issues resolve
*must include the non-mobile devices
 
MTBF
*2.2 support, nightly build test
*think how to support master/M-C
*more debug information
*escalation earlier and work with developer
*help partners to setup, execution and troubleshooting
*test scenarios coverage and review
*Sync information with partners (CAF)
 
ConnDevices
*web api test support
*non-mobile devices support
*MCTS try run
*Stingray test ownership
 
Others:
*requests from other teams
 
==2015 Mid-term==
*Automation
**JavaScript Marionette
*Performance test
**test scenarios and criteria
**working model, flow, resource
***regular report, notification, issue replicate
**Raptor
*Battery consumption
**Setup a lab in TPE
**test scenarios and criteria
**data for released devices
*Emulator support (tbd)
*MozTrap enhancement
*FOTA service
**http://goo.gl/G1PUJl
*Build Bisect tool
**POC first
 
==Long-term==
*TPE members can cover all b2g QA tests
*Team structure
**OS team
**Device team
**Cert team
**Stability team
**A-team
*IOT, partners certification suite setup
** equipments setup and lab construction
*Technical knowledge, domain know how
**b2g
**mobile new technology
**automation related
**testing methodology

Latest revision as of 09:30, 15 March 2016

Members

  • OS support members
    • Eric, Edward, Shing, Hermes, Teri, Gerry, Alison
  • Device Branch members
    • Hubert, William, Mike
  • MCTS, ConnDevices members
    • Al, Askeing, Owen, Cynthia
  • Stability
    • Paul, Walter, Shako

2015 Short-term

OS Support

  • 2.2 release
    • Milestone criteria gatekeeper
    • Provide project health status
    • Balance resource load
    • Increase automation rate
    • Test case review meeting
    • Module ownership
    • Regular Performance report
      • work with EPM to come out the performance scenarios and criteria
  • 2.5
    • Gaia UI test in JavaScript or follow the automation members’ (Geo, Johan) plan
    • Prepare for 2.5

Device branch

  • 2.0M Woodduck
  • 2.1S Dolphin
  • 2.2 new devices branch
  • other devices support
  • Work with 3rd party test lab
  • Device release process
  • Health status

MCTS

  • 2.0, 2.1 release package support and maintenance
  • 2.2 new architecture design and package delivery
    • 2015/06 ship the first package
  • easy to install, execute and troubleshooting
  • web site must be up to date
  • work with partners to have the clear process and help on issues resolve
  • must include the non-mobile devices

MTBF

  • 2.2 support, nightly build test
  • think how to support master/M-C
  • more debug information
  • escalation earlier and work with developer
  • help partners to setup, execution and troubleshooting
  • test scenarios coverage and review
  • Sync information with partners (CAF)

ConnDevices

  • web api test support
  • non-mobile devices support
  • MCTS try run
  • Stingray test ownership

Others:

  • requests from other teams

2015 Mid-term

  • Automation
    • JavaScript Marionette
  • Performance test
    • test scenarios and criteria
    • working model, flow, resource
      • regular report, notification, issue replicate
    • Raptor
  • Battery consumption
    • Setup a lab in TPE
    • test scenarios and criteria
    • data for released devices
  • Emulator support (tbd)
  • MozTrap enhancement
  • FOTA service
  • Build Bisect tool
    • POC first

Long-term

  • TPE members can cover all b2g QA tests
  • Team structure
    • OS team
    • Device team
    • Cert team
    • Stability team
    • A-team
  • IOT, partners certification suite setup
    • equipments setup and lab construction
  • Technical knowledge, domain know how
    • b2g
    • mobile new technology
    • automation related
    • testing methodology