TestEngineering/Performance/Raptor/Browsertime: Difference between revisions

TestEngineering/Performance/Raptor/Browsertime (view source)

Revision as of 18:30, 30 October 2019

200 bytes added , 30 October 2019

Extra upgrading information for when issues are encountered.

Gmierz

83

edits

@@ Line 60: / Line 60: @@
 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 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. There might not be any changes to it. In that case, run <tt>npm install</tt> in <tt>tools/browsertime/</tt> to update it, you should at the least see a change in the "integrity" and "version" fields.
 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.