TestEngineering/Performance: Difference between revisions
Jump to navigation
Jump to search
(Redirected page to Performance/Tools) |
|||
| (72 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
#REDIRECT [[Performance/Tools]] | |||
{{DISPLAYTITLE:Firefox Performance Test Engineering 🔥🦊⏱️}}[[File:Fxperftest.png|thumb|right]] | |||
= | = New contributors = | ||
If you are a new contributor, or would like to start contributing you can find a guide to help you [[/NewContributors|here]]. | |||
= | = Where to find us = | ||
* | * [https://chat.mozilla.org/#/room/#perftest:mozilla.org #perftest] | ||
== | = Team purpose = | ||
To support the infrastructure and creation of automated tests for evaluating the performance of Firefox products. This provides value by exposing gaps in coverage, revealing areas where we can make performance gains, identifying performance regressions in a timely manner, and by providing key performance metrics that assist in determining how Firefox measures against release criteria. | |||
= What we do = | |||
* Identification of gaps in performance test infrastructure and monitoring. | |||
* Designing and building performance test infrastructure and monitoring solutions. | |||
* Supporting Firefox engineers on writing performance tests. | |||
* Supporting Firefox engineers on investigating regressions identified by tests. | |||
* Collaboration with release operations on infrastructure requirements. | |||
* Standing up performance tests in continuous integration environments. | |||
* Monitoring performance test results and identifying potential regressions. | |||
* Supporting performance sheriffs with tools to assist in identifying regressions. | |||
* Developing test plans for performance testing. | |||
* Running adhoc manual or partially automated performance testing. | |||
== | = What we don't do = | ||
* Maintenance of infrastructure hardware. | |||
* Maintain the continuous integration pipeline. | |||
* Writing/maintaining all performance tests. | |||
= Meetings = | |||
{{/Meetings}} | |||
== | = Onboarding = | ||
Welcome to the team! You are encouraged to improve the [[/Onboarding|onboarding page]]. If you need to ask questions that are not already covered, please update the page so that the next person has a better onboarding experience. | |||
= | = Workflow = | ||
* | * [[/Triage Process/]] | ||
* [[/Review Process/]] | |||
* | |||
== | = Projects = | ||
* [[/Fenix/]] | |||
* [[/Raptor/]] | |||
* [[/Raptor/Browsertime/]] | |||
* [[/Talos/]] | |||
== | = Results = | ||
See our {{wip|[[/Results|results page]]}}. | |||
== | = Resources = | ||
* [[/Glossary/]] | |||
* [https://docs.google.com/document/d/1SswqYIAm4h8vlwfMc0pfGEJwXpFECyubGDezRZHHPFE/edit Strategies for investigating intermittents] | |||
* [https://docs.google.com/document/d/1HV2_z8hwhI2w8EbURtkYjpikVG5g9QeKEPo9h5msuRs/edit Following up perf bugs] | |||
* [https://docs.google.com/document/d/103SRVVcE2SZNYP3kFXGeiVQrusH2Wj2yv8SWaDvB9SM/edit Excessive Android device queue response plan] | |||
* [[/FAQ#How_can_I_do_a_bisection.3F|Bisection Workflow]] | |||
* [[/Sheriffing/CompareView|CompareView]] | |||
Latest revision as of 17:57, 24 July 2023
Redirect to:
New contributors
If you are a new contributor, or would like to start contributing you can find a guide to help you here.
Where to find us
Team purpose
To support the infrastructure and creation of automated tests for evaluating the performance of Firefox products. This provides value by exposing gaps in coverage, revealing areas where we can make performance gains, identifying performance regressions in a timely manner, and by providing key performance metrics that assist in determining how Firefox measures against release criteria.
What we do
- Identification of gaps in performance test infrastructure and monitoring.
- Designing and building performance test infrastructure and monitoring solutions.
- Supporting Firefox engineers on writing performance tests.
- Supporting Firefox engineers on investigating regressions identified by tests.
- Collaboration with release operations on infrastructure requirements.
- Standing up performance tests in continuous integration environments.
- Monitoring performance test results and identifying potential regressions.
- Supporting performance sheriffs with tools to assist in identifying regressions.
- Developing test plans for performance testing.
- Running adhoc manual or partially automated performance testing.
What we don't do
- Maintenance of infrastructure hardware.
- Maintain the continuous integration pipeline.
- Writing/maintaining all performance tests.
Meetings
- When: Weekly on Wednesdays at 15:00 UTC (08:00 PST, 11:00 EST, 18:00 EET)
- Where: Zoom ID 110-819-485
- Notes: Google Docs
Onboarding
Welcome to the team! You are encouraged to improve the onboarding page. If you need to ask questions that are not already covered, please update the page so that the next person has a better onboarding experience.
Workflow
Projects
Results
See our 🚧 results page 🚧.