QA/Embedded Teams

For the core Firefox and Platform QA teams we are using an embedding strategy where we have embedded QA engineers alongside engineers in specific functional teams. We are doing this to:

1. Improve the scope and depth of quality engineering in these areas
2. Provide more focus and development more technical acumen on QA
3. Identify strategic areas where involvement results in better overall quality across the board to best use the small number of people we have

The areas where we are working are:

• DOM team (Tracy & Ashughes)
• E10S (multi-process) team (Juanb & Lizzard)
• Security and Privacy team (Kjoziwiak & Mwobensmith)
• Media and Video team (Spolk, Marcia, and Maja)
• Firefox for Android (AaronMT & Kbrosnan)
• Overall QA Releases, Quality Programs, and Risk: Kairo & Mschifer

There are of course other areas that we cannot cover to the degree we would like to and currently have no one embedded in these teams:

• Graphics
• Firefox Front-end
• Developer Tools
• Networking
• JavaScript

As a result there are things that will fall through the cracks. We are working quite hard to analyze the risk of everything that falls through the cracks and ensure that risk is mitigated through some means (contributor, contractor, staff, and/or automation). We will maintain the below list for things that are currently in this zone.

• Reading List (desktop)
• Password Manager (desktop)
• ios product
• windows 64 bit builds
• geolocation changes
• addon signing
• network predictor landing