TestEngineering: Difference between revisions

← Older edit

TestEngineering (view source)

Revision as of 06:11, 13 December 2024

528 bytes removed , 13 December 2024

Formatting

JeanPaulLucien

Confirmed users

514

edits

@@ Line 1: / Line 1: @@
+== Mission Statement ==
-= Overview =
+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.
-Firefox Test Engineering oversees the test automation, infrastructure, and manual testing for all of Firefox's services, sites, and apps that are external to the core browsers (and in some cases within the browsers as well).
 More info is at: http://firefox-test-engineering.readthedocs.io/en/latest/
-= Mission =
+== Focus Areas ==
-Our mission is to provide testing and tools to positively impact the quality of Mozilla sites, apps, and services.
+* Interop
+* Performance
-= The Team =
+* GeckoView
-* Manager: Stuart Philp
+* Fenix
-* Technical Lead and Manager, Customization group: Krupa Raj
+* Amazon
-* Technical Lead, UI group: [https://mozillians.org/u/davehunt/ Dave Hunt]
+* CI Automation
-* Technical Lead, Services group: Richard Pappalardo
+* Ecosystem
-* Staff Engineer: Tarek Ziade
+* Telemetry
-* Manager, Services group: [https://mozillians.org/u/kthiessen Karl Thiessen]
+* Premium Services
-* Senior Test Engineer: Peter deHaan
+* Energy
-* Staff Test Engineer: Chris Hartjes
+* Accessibility
-* Senior Test Engineer: [https://mozillians.org/en-US/u/stephend/ Stephen Donner]
+* Reporting
-* Senior Test Engineer: Kevin Brosnan
+* Monitoring
-* Senior Test Engineer: Aaron Train
+* Experiments
-* Senior Test Engineer: Matt Brandt
-* Senior Test Engineer: Rebecca Billings
-* Senior Test Engineer: No-Jun Park
-* Junior Test Engineer: Benny Forehand Jr.
-=Technical Groups=
-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.
-==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=
+== 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
-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