83
edits
TestEngineering/Performance/Raptor/Browsertime: Difference between revisions
TestEngineering/Performance/Raptor/Browsertime (view source)
Revision as of 15:56, 12 January 2021
, 12 January 2021→Finding the Geckodriver Being Used: Add information about geckodriver builds
(→Page-load tests: Recommend Raptor-Browsertime.) |
(→Finding the Geckodriver Being Used: Add information about geckodriver builds) |
||
| Line 111: | Line 111: | ||
* Find the latest one from here: https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=geckodriver | * Find the latest one from here: https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=geckodriver | ||
* Alternatively, if you're trying to figure out which geckodriver a given CI task is using, you can click on the browsertime task in treeherder, and then click on the `Task` id in the bottom left of the pop-up interface. Then in the window that opens up, click on `See more` in the task details tab on the left, this will show you the dependent tasks with the latest toolchain-geckodriver being used. There's an Artifacts drop down on the right hand side for the toolchain-geckodriver task that you can find the latest geckodriver in. | * Alternatively, if you're trying to figure out which geckodriver a given CI task is using, you can click on the browsertime task in treeherder, and then click on the `Task` id in the bottom left of the pop-up interface. Then in the window that opens up, click on `See more` in the task details tab on the left, this will show you the dependent tasks with the latest toolchain-geckodriver being used. There's an Artifacts drop down on the right hand side for the toolchain-geckodriver task that you can find the latest geckodriver in. | ||
If you're trying to test Browsertime with a new geckodriver, you can do either of the following: | |||
* Request a new geckodriver build in your try run (i.e. through <code>./mach try fuzzy</code>). | |||
* Trigger a new geckodriver in a try push, then trigger the browsertime tests which will then use the newly built version in the try push. | |||
=== Comparing Before/After Browsertime Videos === | === Comparing Before/After Browsertime Videos === | ||