TestEngineering/Performance: Difference between revisions
Jump to navigation
Jump to search
| Line 39: | Line 39: | ||
= Objectives = | = Objectives = | ||
== [https://docs.google.com/ | == 2020/Q1 == | ||
* | * [https://docs.google.com/document/d/1GsK6BwgZyQnXt3H6ZzxmzVHc_b0qzcFKyzC_dz-kFNk/edit# KR3: Perfherder Alerts Enhancements] | ||
* [https://docs.google.com/document/d/10eLFO1ouPzTheIhfcdBy9GapibLDdcbk7DlFOO9_DNY/edit# KR4: Mobile Visual Metrics in CI] | |||
* [https://docs.google.com/document/d/1F7dtFKO_GXTEDq7SBzisNWoG3rmdnIMQ_fiNrCXCT8A/edit# KR5: Auto Backfill Investigation] | |||
* | |||
= Projects = | = Projects = | ||
Revision as of 11:46, 25 January 2020
Who we are
- Dave Hunt [:davehunt] 🇬🇧
- 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
- 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 🚧.