TestEngineering/Performance: Difference between revisions
(→Who we are: :wave) Tags: Mobile edit Mobile web edit |
No edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Firefox Performance Test Engineering 🔥🦊⏱}} | {{DISPLAYTITLE:Firefox Performance Test Engineering 🔥🦊⏱}}[[File:Fxperftest.png|thumb|right]] | ||
= Who we are = | = Who we are = | ||
* Dave Hunt [:davehunt] 🇬🇧 | * Dave Hunt [:davehunt] 🇬🇧 | ||
| Line 12: | Line 13: | ||
= Where to find us = | = Where to find us = | ||
* [https://mozilla. | * [https://chat.mozilla.org/#/room/#perftest:mozilla.org #perftest] | ||
= What we do = | = What we do = | ||
Revision as of 11:40, 25 January 2020
Who we are
- Dave Hunt [:davehunt] 🇬🇧
- Rob Wood [:rwood] 🇨🇦
- Greg Mierzwinski [:sparky] 🇨🇦
- Ionuț Goldan [:igoldan] 🇷🇴
- Florian Strugariu [:bebe] 🇷🇴
- Marian Raiciof [:marauder] 🇷🇴
- Alex Ionescu [:alexandrui] 🇷🇴
- Alex Irimovici [:air] 🇷🇴
- Octavian Negru [:onegru] 🇷🇴
Where to find us
What we do
We provide automated testing support for measuring the performance of Firefox products. Here are a few examples of what you can expect our team to be working on.
- Provide advice/troubleshooting related to performance testing or any of our tools and harnesses.
- Develop test plans that involve automation of performance testing.
- Prototype, build, and maintain test harnesses for performance testing.
- Monitoring and reporting of performance regressions.
What we don't do
- Own all performance tests. We work on the test harnesses and tools that are used for performance testing, but the tests themselves are often developed outside of our team. Every test should have an owner, who is responsible for responding to questions related to the test, and may be asked to assist when the test detects a regression.
- Review all performance tests. Similar to test ownership, we enable others to contribute performance tests. We can provide advice and reviews, but do not impose this as a restriction to landing test changes.
- Maintain the infrastructure the tests run on
- Maintain the continuous integration pipeline
- Maintain the reporting tools
Meetings
The team meets every Wednesday, alternating format based on the week number. The current week number is 4.
- Where: Zoom
- Recordings: Team Meetings
Team Chat (odd-numbered weeks)
A lightweight check-in to connect as a team. We focus on informal discussion and a "Question of the Week" to get to know each other better.
- When: 15:45 - 16:00 (UTC)
- Notes: Google Doc
Team Meeting (even-numbered weeks)
Our regular team meeting covering announcements, reminders, discussion items, learnings, appreciations, KPI updates, and project updates. We always close with a "Question of the Week".
- When: 15:30 - 16:15 (UTC)
- Notes: Google Doc
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
2019/Q3
- KR1.3: Fenix Startup Test Development [rwood] [NOT STARTED] [%]
- KR3.1: Video QoE testing for desktop [marauder] [ON TRACK] [90%]
- KR3.2: Video QoE testing for Fenix [marauder] [DONE] [100%]
- KR3.4: Complete MVP for browsertime in CI [rwood] [ON TRACK] [90%]
- KR4.1: Migrate CI from Chromium to Chrome [sparky] [CHALLENGED] [40%]
- KR4.2: Power tests on macOS laptops [sparky] [ON TRACK] [95%]
- KR6.6: Improve perf sheriff efficiency [igoldan] [ON TRACK] [80%]
Projects
Results
See our 🚧 results page 🚧.