TestEngineering: Difference between revisions
Jump to navigation
Jump to search
StuartPhilp (talk | contribs) (remove section) |
StuartPhilp (talk | contribs) (new team structure) |
||
| Line 43: | Line 43: | ||
** Relationship building | ** 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 | |||
Revision as of 16:31, 22 January 2019
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