TestEngineering: Difference between revisions
Jump to navigation
Jump to search
StuartPhilp (talk | contribs) (Created page with "Placeholder, more to come. Firefox Test Engineering oversees the test automation, infrastructure, and manual testing for all of Firefox's services, sites, and apps that are e...") |
(Formatting) |
||
| (95 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
== 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 | |||
<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