Confirmed users
355
edits
TestEngineering/Performance/Raptor/Browsertime: Difference between revisions
TestEngineering/Performance/Raptor/Browsertime (view source)
Revision as of 15:29, 10 September 2019
, 10 September 2019→Running Browsertime on Try
No edit summary |
Nalexander (talk | contribs) |
||
| Line 39: | Line 39: | ||
[https://github.com/mozilla/browsertime/tree/master/docs/examples Browsertime docs] | [https://github.com/mozilla/browsertime/tree/master/docs/examples Browsertime docs] | ||
=== Running Browsertime on Try === | === Running Browsertime on Try === | ||
Include the `--browsertime` flag to `mach try fuzzy`. As of [https://bugzilla.mozilla.org/show_bug.cgi?id=1566174 bug 1566174] this will arrange for the jobs to include dependencies for Browsertime (Node.js, Browsertime `node_modules`, `geckodriver`, `chromedriver`, etc) and for the Raptor harness to run the given pageload test using Browsertime. | |||
'''Not all Raptor tasks use Browsertime meaningfully. Right now, only cold pageload tests are supported.''' See [https://bugzilla.mozilla.org/show_bug.cgi?id=1577905 bug 1577905] for warm pageload tests, for example. | |||
For example: | |||
./mach try fuzzy --browsertime -q "'test-android-hw-g5-7-0-arm7-api-16/opt-raptor-tp6m-1-geckoview-e10s" | |||
=== Bugs === | === Bugs === | ||