TestEngineering: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(remove section)
(Formatting)
 
(One intermediate revision 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


= Enduring Objectives =
== Enduring Objectives ==
* Increase visibility into product risks
* Increase visibility into product risks
** Streamline reporting
** Streamline reporting
Line 43: Line 41:
** Relationship building
** Relationship building


=Technical Groups=
== People ==
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.
Director: Stuart Philp
 
<br>Architect: Tarek Ziade
==User Interfaces==
<br>Interop. Manager: David Burns
* https://wiki.mozilla.org/TestEngineering/UI
<br>Performance. Manager: Dave Hunt
* Lead: Dave Hunt
<br>Ecosystem. Manager: Krupa Raj
 
<br>CI Automation. Manager: Joel Maher
==Services==
<br>Mobile. Manager: No-Jun Park
* https://wiki.mozilla.org/TestEngineering/Services
* Lead: Richard Pappalardo
* Manager: Karl Thiessen
 
==Customization==
* https://wiki.mozilla.org/TestEngineering/Customization
* Lead: Krupa Raj

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"