MozillaWiki

TestEngineering/Performance: Difference between revisions

Page Discussion

TestEngineering/Performance (view source)

Revision as of 17:57, 24 July 2023

654 bytes removed ,  24 July 2023
Redirected page to Performance/Tools
(Added a top-level page for Fenix testing.)
(Redirected page to Performance/Tools)
Β 
(28 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Firefox Performance Test Engineering πŸ”₯🦊⏱}}
#REDIRECT [[Performance/Tools]]
= Who we are =
Β 
* Dave Hunt [:davehunt] πŸ‡¬πŸ‡§
{{DISPLAYTITLE:Firefox Performance Test Engineering πŸ”₯🦊⏱️}}[[File:Fxperftest.png|thumb|right]]
* Stephen Donner [:stephend] πŸ‡ΊπŸ‡Έ
Β 
* Rob Wood [:rwood] πŸ‡¨πŸ‡¦
= New contributors =
* Greg Mierzwinski [:sparky] πŸ‡¨πŸ‡¦
Β 
* IonuΘ› Goldan [:igoldan] πŸ‡·πŸ‡΄
If you are a new contributor, or would like to start contributing you can find a guide to help you [[/NewContributors|here]].
* Florian Strugariu [:bebe] πŸ‡·πŸ‡΄
* Marian Raiciof [:marauder] πŸ‡·πŸ‡΄
* Alex Ionescu [:alexandrui] πŸ‡·πŸ‡΄
* Alex Irimovici [:air] πŸ‡·πŸ‡΄
* Octavian Negru [:onegru] πŸ‡·πŸ‡΄


= Where to find us =
= Where to find us =
* [https://mozilla.slack.com/ Slack]: #perftest
* [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 =
= 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.
* Identification of gaps in performance test infrastructure and monitoring.
* Provide advice/troubleshooting related to performance testing or any of our tools and harnesses.
* Designing and building performance test infrastructure and monitoring solutions.
* Develop test plans that involve automation of performance testing.
* Supporting Firefox engineers on writing performance tests.
* Prototype, build, and maintain test harnesses for performance testing.
* Supporting Firefox engineers on investigating regressions identified by tests.
* Monitoring and reporting of performance regressions.
* 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 =
= 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.
* Maintenance of infrastructure hardware.
* 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 continuous integration pipeline.
* Maintain the infrastructure the tests run on
* Writing/maintaining all performance tests.
* Maintain the continuous integration pipeline
* Maintain the reporting tools


= Meetings =
= Meetings =
Line 36: Line 37:


= Workflow =
= Workflow =
* [[/Task Workflow/]]
* [[/Triage Process/]]
* [[/Triage Process/]]
Β 
* [[/Review Process/]]
= Objectives =
Β 
== [https://docs.google.com/spreadsheets/d/1P1d7rzA27t3OHljraxapNgDl-1Hsc_novoj78w8qog0/edit#gid=584732224 2019/Q3] ==
* KR1.3: Fenix Startup Test Development [rwood] {{notstarted|}} [%]
* KR3.1: Video QoE testing for desktop [marauder] {{ok|}} [90%]
* KR3.2: Video QoE testing for Fenix [marauder] {{done|}} [100%]
* KR3.4: Complete MVP for browsertime in CI [rwood] {{ok|}}Β  [90%]
* KR4.1: Migrate CI from Chromium to Chrome [sparky] {{challenged|}} [40%]
* KR4.2: Power tests on macOS laptops [sparky] {{ok|}} [95%]
* KR6.6: Improve perf sheriff efficiency [igoldan] {{ok|}} [80%]


= Projects =
= Projects =
* [[/NimbleDroid/]]
* [[/Fenix/]]
* [[/Fenix/]]
* [[/Raptor/]]
* [[/Raptor/]]
* [[/Raptor/Browsertime/]]
* [[/Raptor/Browsertime/]]
* [[/Talos/]]
* [[/Talos/]]
* [[/WebPageTest/]]


= Results =
= Results =
Line 66: Line 54:
* [https://docs.google.com/document/d/1HV2_z8hwhI2w8EbURtkYjpikVG5g9QeKEPo9h5msuRs/edit Following up perf bugs]
* [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]
* [https://docs.google.com/document/d/103SRVVcE2SZNYP3kFXGeiVQrusH2Wj2yv8SWaDvB9SM/edit Excessive Android device queue response plan]
* [https://docs.google.com/document/d/1jVSaTlMZx-9DCjJurDpZJElm3yxN7N3OyjVh7hmwBb4/edit Perf bisection workflows]
* [[/FAQ#How_can_I_do_a_bisection.3F|Bisection Workflow]]
* [[/Sheriffing/CompareView|CompareView]]
Davehunt
Confirmed users
2,177

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1219036...1247190"