QA/Firefox

From MozillaWiki
< QA
Jump to: navigation, search

Overview

This material is largely out of date

The Firefox QA team is responsible for the Firefox browser -- both Desktop, (Windows, Linux, Mac) and Mobile (Android). Our responsibilities include qualifying builds prior to a maintenance or milestone release. Other 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 and user-facing 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.

Community

Everyone is welcome to join us in testing and in our weekly meetings.

If you would like to help out, pick a task from One and Done, which has a list of ways to start testing. All the tasks are up-to-date and they have clear, step by step instructions!

Team Meetings

This team has been broken up and is embedded with the development teams. Channel Meetings is the best place to get an overview of what individuals are working on.

Meeting Notes

Team Members and Assignments

Firefox QA Team - July 2014 Work Week
Front:Matt,Juan,Gaby,Liz
Back:Nils,Kamil,KaiRo,Anthony,Tracy,Kevin,Marc,Aaron
Not Pictured: Henrik

SoftVision QA Team

SoftVision QA Team

Community members

Here are a few of our active community members!

Name Contact Roles
Gabriela Montagu gaby2300 Contributor in QA and Mozilla Hispano; testdays
Francesca Ciceri madamezou Firefox QE contributor, 2014 OPW intern
Tiziana Sellitto tiziana Firefox QE contributor, 2013 OPW intern, triage workshops, addon developer
Andre Klapper andre Bug triage, Wikimedia bug wrangler, Bugzilla project
Aleksej Aleksej Bug triage, verification, Bugday moderator, channel op for #bugday
Jayakumar Sadhasivam iamjayakumars Bug triage, Nightly tester, Firefox OS tester, SUMO

Feature Owners

Major features in Firefox are owned by a primary QA contact who is responsible for ensuring the proper testing of those features.

We encourage community members to try specializing in a particular Firefox feature so they gain knowledge in depth! Contact the feature owner if you would like to be a tester on their team.

Here's our current list of Feature Owners.

Release Owners

(M) = Mobile, (D) = Desktop

Nightly (N) Fx34 Fx 35 Fx 36 Fx 37 Fx 38 Fx 39 Fx 40
Aurora (A) Fx33 Fx 34 Fx 35 Fx 36 Fx 37 Fx 38 Fx 39
Beta (B) Fx32 Fx 33 Fx 34 Fx 35 Fx 36 Fx 37 Fx 38
Owner July 22-Sept1 Sept 2-Oct 13 Oct 14-Nov 24 Nov 25 -Jan 5 Jan 6th – Feb 16 Feb 17- Mar 30 Mar 31 – May 11
Anthony Fx34(D) N Fx35(M) N Fx35(M) A Fx35(M) B Off Fx39(D) N Fx39(D) N Fx39(D) N
Aaron Fx32(M)/Fx34(M) Fx34(M) A Fx34(M) B Off Fx38(M) N Fx38(M) N Fx38(M) N
Kevin Fx33(M) A Fx33(M) B Off Fx37(M) N Fx37(M) A Fx37(M) B Fx 40(D) N Fx 40(D) A Fx 40(D) B
Juan Fx32(D) B Off – e10s prep Fx 36(D) e10s N Fx 36(D) e10s A Fx 36(D) e10s B Fx39(M) N Fx39(M) N Fx39(M) N
KaiRo Off Fx35(D) N Fx35(D) A Fx35(D) B Fx38(D) N Fx38(D) N Fx38(D) N
Liz Fx34(D) N Fx34(D) A Fx34(D) B Fx37(D) N Fx37(D) N Fx37(D) N Off
Tracy Fx33(D) A Fx33(D) B Fx36(M) N Fx36(M) A Fx36(M) B Off Fx 40(M) N Fx 40(M) A Fx 40(M) B

Release test plans

Project Test Plan Description Scope Timeframe
Firefox 37
Firefox for Android 37 		QA activities for Firefox 37. Features in Fx37
Features in Firefox for Android 37 		Firefox 37
Firefox 36
Firefox for Android 36 		QA activities for Firefox 36. Features in Fx36
Features in Firefox for Android 36 		Firefox 36
Firefox 35
Firefox for Android 35 		QA activities for Firefox 35. Features in Fx35
Features in Firefox for Android 35 		Firefox 35
Firefox 34
Firefox for Android 34 		QA activities for Firefox 34. Features in Fx34
Features in Firefox for Android 34 		Firefox 34
Automation Development of automated tests for Desktop Firefox features using Mozmill
Feature Ownership Testing, Planning, and Bug Triage of new and stable Firefox features


Older test plans are archived here: QA/Past Test Plans

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

Automation

Test automation!

The Firefox Automation team is a group of passionate and open minded people working on automation for Firefox. We are spread around the world, but we have one collective goal to empower automation even more in the Mozilla project. If you want to get in contact with one of us please check the table below for more information.

https://wiki.mozilla.org/QA/Automation

Stability

The Crashkill or Stability team! https://wiki.mozilla.org/CrashKill

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Firefox&oldid=1117582"