15
edits
TestEngineering/Performance/Sheriffing: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing (view source)
Revision as of 12:03, 26 February 2020
, 26 February 2020Added a video for Overview section
Alexandrui (talk | contribs) |
(Added a video for Overview section) |
||
| Line 3: | Line 3: | ||
A Performance Sheriff's job is similar: to make sure that performance regressions in Firefox are detected and dealt with. They look at the data produced by performance test jobs (mainly Talos), find regressions, determine their root cause(s) and gets bugs on file to track all issues and make interested parties aware of what is going on. | A Performance Sheriff's job is similar: to make sure that performance regressions in Firefox are detected and dealt with. They look at the data produced by performance test jobs (mainly Talos), find regressions, determine their root cause(s) and gets bugs on file to track all issues and make interested parties aware of what is going on. | ||
A short demo describing the performance sheriffing workflow: | |||
https://youtu.be/VdTC7Maa6hE | |||
= What is an alert = | = What is an alert = | ||