TestEngineering/Performance: Difference between revisions
Jump to navigation
Jump to search
(Add link to new contributors section.) |
|||
| Line 13: | Line 13: | ||
* Marian Raiciof [:marauder] π·π΄ | * Marian Raiciof [:marauder] π·π΄ | ||
* Octavian Negru [:onegru] π·π΄ | * Octavian Negru [:onegru] π·π΄ | ||
= New Contributors = | |||
If you are a new contributor, or would like to start contributing you can find a guide to help you [https://wiki.mozilla.org/TestEngineering/Performance/NewContributors here]. | |||
= Where to find us = | = Where to find us = | ||
Revision as of 18:30, 12 February 2020
Who we are
- Kimberly Sereduck [:kimberlythegeek] πΊπΈ
- Greg Mierzwinski [:sparky] π¨π¦
- Maja Frydrychowicz [:maja_zf] π¨π¦
- Dave Hunt [:davehunt] π¬π§
- Henrik Skupin [:whimboo] π©πͺ
- Alex Ionescu [:alexandrui] π·π΄
- Alex Irimovici [:air] π·π΄
- Florian Strugariu [:bebe] π·π΄
- IonuΘ Goldan [:igoldan] π·π΄
- Marian Raiciof [:marauder] π·π΄
- Octavian Negru [:onegru] π·π΄
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
Objectives
2020/Q1
- KR3: Perfherder Alerts Enhancements
- KR4: Mobile Visual Metrics in CI
- KR5: Auto Backfill Investigation
Projects
Results
See our π§ results page π§.