TestEngineering: Difference between revisions
Jump to navigation
Jump to search
StuartPhilp (talk | contribs) (revised focus areas) |
StuartPhilp (talk | contribs) (team objectives) |
||
| Line 22: | Line 22: | ||
* Experiments | * 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 | |||
=Technical Groups= | =Technical Groups= | ||
Revision as of 16:26, 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
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
The source of truth for FTE Projects is our Servicebook. The table below may be out of date.