TestEngineering/Performance/Raptor/Browsertime: Difference between revisions

Jump to navigation Jump to search
Add information on finding latest geckodriver.
(Add information on finding latest geckodriver.)
Line 96: Line 96:


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.
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.
=== Finding the Geckodriver Being Used ===
If you're looking for the latest geckodriver being used there are two ways:
* 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.


=== Bugs ===
=== Bugs ===
97

edits

Navigation menu