83
edits
TestEngineering/Performance/Raptor/Browsertime: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Raptor/Browsertime (view source)
Revision as of 18:00, 30 October 2019
, 30 October 2019Add browsertime tarball upgrading information.
No edit summary |
(Add browsertime tarball upgrading information.) |
||
| Line 55: | Line 55: | ||
For example: | For example: | ||
./mach try fuzzy --browsertime -q "'test-android-hw-g5-7-0-arm7-api-16/opt-raptor-tp6m-1-geckoview-e10s" | ./mach try fuzzy --browsertime -q "'test-android-hw-g5-7-0-arm7-api-16/opt-raptor-tp6m-1-geckoview-e10s" | ||
=== Upgrading Browsertime In-Tree === | |||
To upgrade the browsertime version used in-tree follow the changes in [https://bugzilla.mozilla.org/show_bug.cgi?id=1592400 bug 1592400]. | |||
To perform the upgrade, you need to make a change to [https://dxr.mozilla.org/mozilla-central/source/tools/browsertime/package.json?q=tools%2Fbrowsertime%2Fpackage.json&redirect_type=direct#8 <tt>tools/browsertime/package.json</tt>] where you need to change the commit of the browsertime tarball. After making the change, upgrade browsertime locally, then include the <tt>tools/browsertime/package-lock.json</tt> changes in the upgrade patch. | |||
To test the upgrade, first run <tt>./mach browsertime https://sitespeed.io</tt> and compare the before/after results. Ensure that --video still works on the upgraded version as well. If all that works, then run all browsertime tests available in production. If everything looks normal, or expected, then the upgrade is good to land. | |||
=== Bugs === | === Bugs === | ||