Refactor the raptor-webext test INI and taskcluster configs
Categories
(Testing :: Raptor, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: rwood, Unassigned)
References
Details
Consider refactoring the raptor-webext test INIs and taskcluster configs in the similar method that was done for the browsertime-tp6 tests in Bug 1590561.
Note that refactoring the existing raptor-webext test INIs/configs would change the subtests names; which in turn would break the dashboards as well as start a new data set in perfherder / start over with automated regression alerts etc.
Also consider how to handle the 'measure' test INI option as in raptor-webext we specify what to measure in each page-load. Consider just measuring all measurement types for all pages (except when it comes to Firefox vs Chrome).
This also depends on if/when we decide to port over the existing raptor-webext tests to browsertime (in which case we'll just use the format already used by the browsertime tests).
Comment 1•5 years ago
•
|
||
We'll be moving from raptor-webext to browsertime in H2/2020, so there's no value in refactoring the existing raptor-webext manifests.
Description
•