TestEngineering: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(revised focus areas)
(Formatting)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
== Mission Statement ==
= Mission Statement =
The Test Engineering team supports the larger Firefox organization by enabling identification of risk to our products and eliminating quality related blind spots through tooling, testing, automation, benchmarks, and reporting.
The Test Engineering team supports the larger Firefox organization by enabling identification of risk to our products and eliminating quality related blind spots through tooling, testing, automation, benchmarks, and reporting.


More info is at: http://firefox-test-engineering.readthedocs.io/en/latest/
More info is at: http://firefox-test-engineering.readthedocs.io/en/latest/


= Focus Areas =
== Focus Areas ==
 
* Interop
* Interop
* Performance
* Performance
Line 22: Line 20:
* Experiments
* Experiments


= The Team =
== Enduring Objectives ==
* Manager: Stuart Philp
* Increase visibility into product risks
* Technical Lead and Manager, Customization group: Krupa Raj
** Streamline reporting
* Technical Lead, UI group: [https://mozillians.org/u/davehunt/ Dave Hunt]
** Reduce blind spots
* Technical Lead, Services group: Richard Pappalardo
* Improve efficiency and clarity of risk assessments
* Staff Engineer: Tarek Ziade
** Tight feedback loops
* Manager, Services group: [https://mozillians.org/u/kthiessen Karl Thiessen]
** Be opinionated (i.e binary or traffic light recommendations)
* Senior Test Engineer: Peter deHaan
** Reduce guesswork, roundtrips
* Staff Test Engineer: Chris Hartjes
** Standardize between projects and types of reports
* Senior Test Engineer: [https://mozillians.org/en-US/u/stephend/ Stephen Donner]
* Maintain or improve coverage and quality standards
* Senior Test Engineer: Kevin Brosnan
** Identify and fill gaps
* Senior Test Engineer: Aaron Train
** Document and measure existing work
* Senior Test Engineer: Matt Brandt
** Establish/Improve release criteria consistency
* Senior Test Engineer: Rebecca Billings
** Reduce effort on maintenance
* Senior Test Engineer: No-Jun Park
* Reduce cross-functional friction
* Junior Test Engineer: Benny Forehand Jr.
** Advocacy
 
** Reporting
=Technical Groups=
** Tools
Firefox Test Engineering is divided into three technical groups. These groups align on the skills, tools, and focus needed to provide the coverage and quality for the projects they oversee. Each technical group has a technical lead, who oversees all of the project's testing needs and best practices.
** Benchmarks
 
** Relationship building
==User Interfaces==
* https://wiki.mozilla.org/TestEngineering/UI
* Lead: Dave Hunt
 
==Services==
* https://wiki.mozilla.org/TestEngineering/Services
* Lead: Richard Pappalardo
* Manager: Karl Thiessen
 
==Customization==
* https://wiki.mozilla.org/TestEngineering/Customization
* Lead: Krupa Raj
 
=Full Project List=


The source of truth for FTE Projects is our [https://servicebook.stage.mozaws.net Servicebook]. The table below may be out of date.
== People ==
Director: Stuart Philp
<br>Architect: Tarek Ziade
<br>Interop. Manager: David Burns
<br>Performance. Manager: Dave Hunt
<br>Ecosystem. Manager: Krupa Raj
<br>CI Automation. Manager: Joel Maher
<br>Mobile. Manager: No-Jun Park

Latest revision as of 06:11, 13 December 2024

Mission Statement

The Test Engineering team supports the larger Firefox organization by enabling identification of risk to our products and eliminating quality related blind spots through tooling, testing, automation, benchmarks, and reporting.

More info is at: http://firefox-test-engineering.readthedocs.io/en/latest/

Focus Areas

  • Interop
  • Performance
  • GeckoView
  • Fenix
  • Amazon
  • CI Automation
  • Ecosystem
  • Telemetry
  • Premium Services
  • Energy
  • Accessibility
  • Reporting
  • Monitoring
  • Experiments

Enduring Objectives

  • Increase visibility into product risks
    • Streamline reporting
    • Reduce blind spots
  • Improve efficiency and clarity of risk assessments
    • Tight feedback loops
    • Be opinionated (i.e binary or traffic light recommendations)
    • Reduce guesswork, roundtrips
    • Standardize between projects and types of reports
  • Maintain or improve coverage and quality standards
    • Identify and fill gaps
    • Document and measure existing work
    • Establish/Improve release criteria consistency
    • Reduce effort on maintenance
  • Reduce cross-functional friction
    • Advocacy
    • Reporting
    • Tools
    • Benchmarks
    • Relationship building

People

Director: Stuart Philp
Architect: Tarek Ziade
Interop. Manager: David Burns
Performance. Manager: Dave Hunt
Ecosystem. Manager: Krupa Raj
CI Automation. Manager: Joel Maher
Mobile. Manager: No-Jun Park

Retrieved from "https://wiki.mozilla.org/index.php?title=TestEngineering&oldid=1252953"