TestEngineering/Performance/Sheriffing/CompareView: Difference between revisions

← Older edit

TestEngineering/Performance/Sheriffing/CompareView (view source)

Revision as of 11:10, 26 February 2020

316 bytes added , 26 February 2020

Added new sections, images and a video link

Mraiciof

15

edits

@@ Line 1: / Line 1: @@
 == What? ==
 While graph view offers a broader perspective on the test results with a two-dimensional view, the compare view offers a more analytical perspective on 2 specific commits or over an aggregation of values. The revisions to compare against could be chosen from different repos.
+Compare View can be used for various situations, a few examples here:
+* when we perform a bisection and we want to analyze the difference between two try pushes, baseline vs backout to find out which changeset introduced the regression
+* when we create a patch and we want to check if the new changes fixed/improved a regression
 == Where? ==
-Compare view is located in the menu of perfherder app.
+Compare view is located in the menu of perfherder app.<br />
-Insert screenshot here
+<br />
+[[File:Compare view page.png|Compare View Screenshot]]
+<br />
 == Why? ==
-Compare view offers a detailed end-to-end analysis over test results, including subtests, deltas, and magnitude of the difference.
+Compare view offers a detailed end-to-end analysis over test results, including subtests, deltas, and magnitude of the difference.<br />
+[[File:Compare view detailed comparison.png|Detailed comparison between two revisions]]
+<br />
 == How? ==
-[steps on how to chose revisions to compare, framework, howto retrigger, change page title etc.]
+Below you can watch a video describing the steps to choose revisions to compare, framework, how to retrigger, etc.
-Let’s assume we have a regression alert created on perfherder.
-To use the compare view for this alert we need 3 things:
+[https://www.youtube.com/embed/dhQwcgwVvec Compare View Demo]
-* the project (mozilla-central, autoland, etc.)
-* first changeset (for the regression)
-* second changeset (for the improvement)