QA/Browser Technologies

From MozillaWiki
< QA
Revision as of 18:15, 16 December 2010 by Tchung (talk | contribs) (→‎Meetings)
Jump to navigation Jump to search

Browser Technologies QA Team Overview

As mobile and Web Services become more prominent in the mozilla project, QA continues to strive to cover and test the projects forthcoming. The current projects with coverage include Test Pilot, Firefox Sync, Jetpack, and Mobile Firefox.

Team Details

Provide explanation of how the team is composed. Does it consist of only Mozilla employees? Does the Team depend on part time resources of other team members

The QA team of Web services and mobile, guided by Tony Chung, coordinates a various set of tasks from feature test development to release testing on different platforms. Since many of these groups are still under 2 years old, there are still developmental progress with automation support and conducted processes. In addition, there are some outsourced work that run nightly smoketests and bug verifications on an ongoing basis.

Team Members and Assignments

Name Contact Availability Project Assignments
Tony Chung tchung@mozilla.com 408-829-8847 MoCo Employee (full time) QA Team Manager
Aakash Desai adesai@mozilla.com 408-829-9187 MoCo Employee (full time) Lead - Mobile Firefox, PM - Input/QMO/Litmus, Community outreach
Tracy Walker twalker@mozilla.com MoCo Employee (full time) Lead - Firefox Sync, Test Pilot, Sr.QA - Firefox features, Litmus testcase management
Martijn Wargers mwargers@mozilla.com MoCo Employee (full time) Sr.QA Fennec automation, testcase reduction expert, crash analysis
Naoki Hirata nhirata@mozilla.com MoCo Employee (full time) QA Engineer - Mobile Firefox, Fennec automation
Ayan Shah ashah@mozilla.com MoCo Employee (intern) Jetpack QA, Sync Automation, mobile firefox, Firefox features
Adriana Hoza ahoza@softvision.ro Waverley (Contract Agency) Mobile Firefox and Desktop Firefox Test Execution
Vlad Maniac vlad.maniac@softvision.ro Waverley (Contract Agency) Mobile Firefox and Desktop Firefox Test Execution

Status

  • Fennec: 2.0 (android + maemo) targeting beta 1 end of September
  • Firefox Sync: targeting Fx4 beta 6
  • Test Pilot: landed in Fx4 beta 1
  • Jetpack: targeting 1.0 end of December
  • Firefox Home: targeting 1.0.2 asap (apple signoff)

Calendar

Meetings

bi-monthly status meetings

 Dial In: 800-707-2533 conf 265
 Every other thursday at 1pm PDT
 Zombocom Conference Room (3rd Floor)
 irc.mozilla.org #qa for backchannel

Team Goals

Current Projects

This section should contain a list to the active current team project page. The section will be included as part of the top level QA organization page.

Project Description
Fennec 2.0 Test Plan Mobile Firefox QA site summarizing Test Strategy, Feature set, assignments, Milestone Testplans, and schedules
Firefox Sync Test Plan Firefox Sync site (both extension and Integrated feature) summarizing Test strategy, testcases, Milestone testplans, and schedules
Test Pilot Test Plan Test Pilot QA site summarizing Test strategy, testcases, Milestone testplans, and schedules
Jetpack Test Plan Jetpack QA site summarizing Test strategy, testcases, Milestone testplans, and schedules
Firefox Home Test Plan Firefox Home (aka Iphone Sync App) site summarizing Test strategy, testcases, Milestone testplans, and schedules


Community Contribution

Anyone can participate. There are several ways in which YOU can participate:

  • File bugs
  • Triage bugs (confirm existing bugs and assign them to the right buckets)
  • Help test new features
  • Write test cases
  • Plan new features testing
  • Help others who want to get involved.

Resources

Reference Links

add links to pertinent wiki pages, blogs, dev project pages, internet sites etc. If team has a number of projects, then it may be more appropriate to list reference links that are specific to the project in the project page itself.

Documentation

add link to any permanent documentation for the team or projects

Archive

A link to a page that contains out of date projects, resources etc. Things we don't want to lose the links to, but are not currently relevant.