TestEngineering/Performance/Sheriffing/CompareView: Difference between revisions
(To add description) |
(Changes on Description) |
||
| Line 8: | Line 8: | ||
== How? == | == How? == | ||
[steps on how to chose revisions to compare, framework, howto retrigger, change page title etc.] | [steps on how to chose revisions to compare, framework, howto retrigger, change page title etc.] | ||
Let’s assume we have a regression alert created on perfherder. | |||
To use the compare view for this alert we need 3 things: | |||
- the project (mozilla-central, autoland, etc.) | |||
- first changeset (for the regression) | |||
- second changeset (for the improvement) | |||
Revision as of 09:38, 26 February 2020
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.
Where?
Compare view is located in the menu of perfherder app. Insert screenshot here
Why?
Compare view offers a detailed end-to-end analysis over test results, including subtests, deltas, and magnitude of the difference.
How?
[steps on how to chose revisions to compare, framework, howto retrigger, change page title etc.] Let’s assume we have a regression alert created on perfherder.
To use the compare view for this alert we need 3 things: - the project (mozilla-central, autoland, etc.) - first changeset (for the regression) - second changeset (for the improvement)