QA/Desktop Firefox

Overview

The team focuses on testing current and upcoming releases of Firefox. Some of our responsibilities include qualifying builds prior to a maintenance or milestone release. Some of the responsibilities include, but are not limited to:

• Verifying bugs using a triage strategy
• Running basic functional tests and smoke tests - automated and manual
• Running our automated test suites on localized builds
• Running automated update tests across platforms, through all update paths, across localized builds
• Making sure web content is ready for consumption

In addition to qualifying builds prior to a release, we perform ongoing tasks on the development branches to ensure no major problems get uplifted as we merge changes to the next branch. For example, on a daily basis we:

• Confirm new unconfirmed bugs
• Verify bugs on development branches like Aurora and Beta
• Engage community and new volunteers in helping improve Firefox through test day events
• Interact with developers to help them test the features they implement
• Perform exploratory testing on new features while on the Aurora branch
• Write test cases in Litmus for new features
• Monitor crash-stats to assess stability
• File and track new crasher bugs as they appear in crash-stats
• Manage web compatibility testing through community involvement or crowdsourcing companies that help in testing hardware configurations and top-site testing

All of which help assess the quality of individual new features as well as the Firefox version as a whole.

Team Details

The team is lead by Juan Becerra who coordinate testing of their respective areas among several MoCo employees and community volunteers. Traditionally new features are tested by several MoCo QA employees, while maintenance releases are tested by Al and a handful of people depending on availability. Anyone is welcome and encouraged to participate.

• Lead - Firefox.next: Juan Becerra (juanb)
• Lead - Sustained Releases: Anthony Hughes (ashughes)

Team Members and Assignments

Name	Contact	Availability	Project Assignments
Juan Becerra	jbecerra@mozilla.com 650-903-0800 x262	MoCo Employee (full time)	Lead - New features testing coordination.
Anthony Hughes	ahughes@mozilla.com	MoCo Employee (full time)	Lead - Maintenance and security releases.
Tracy Walker	twalker@mozilla.com	Moco Employee (full time)	Firefox Sync QA Lead for Desktop and Mobile
Matt Wobensmith	mwobensmith@mozilla.com	Moco Employee (full time)	Senior QA for Desktop, security and privacy
Liz Henry	lhenry@mozilla.com	Moco Employee (full time)	Bug Master and crash analysis.
Henrik Skupin	hskupin@mozilla.com	Moco Employee (full time)	Lean - Test Automation.
Marc Schifer	mschifer@mozilla.com	Moco Employee (full time)	Senior Manager for Desktop QA

Staff Meetings

QA/Desktop_Firefox/StaffMeetings

Security Triage Team

The primary purpose of this team is to verify security fixes for Firefox releases. If you want to be someone who is committed to helping with security fix verification during the Beta release cycle, please add your name below. If you are interested in being part of this team but don't have the skills or bugzilla access, please contact Anthony Hughes.

Members

• Matt Wobensmith (irc: mwobensmith)
• Anthony Hughes (irc: ashughes) [Lead]
• Geo Mealer (irc: geo)
• Jason Smith (irc: jsmith)

Current Work

• Firefox 21 Beta: Test Plan

Current Projects

Project Test Plan	Description	Scope	Timeframe
Firefox 21	QA activities revolving around Firefox Beta in the time frame for Firefox 21 final release.	Features in Fx21	May 14th, 2013 (beta).
Firefox 22	QA activities revolving around mozilla-aurora in the time frame for Firefox 22 merge to beta.	Features in Fx22	June 25th, 2013 (aurora).
Firefox 23	QA activities revolving around mozilla-central in the time frame for Firefox 23 merge to aurora.	Features in Fx23	August 6th, 2013 (nightly).
Automation	Development of automated tests for Desktop Firefox features using Mozmill
Feature Ownership	Testing, Planning, and Bug Triage of new and stable Firefox features

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

• This is a list of all the features being considered for development across products in the near future: https://wiki.mozilla.org/Features.
  • To be specific this is the list of desktop Firefox features being considered.
• You can find a list of features to be shipped in the coming milestones: https://wiki.mozilla.org/Firefox/Flight_Tracking

Archive

• Desktop Firefox QA Team Calendar.
• Old Meeting Notes