Confirmed users
9,511
edits
TestEngineering/Performance/Raptor: Difference between revisions
Jump to navigation
Jump to search
→Power-Usage Tests (Android)
| Line 100: | Line 100: | ||
* We set `scenario_time` to '''20 minutes''' (1200000 milliseconds), and `page_timeout` to '22 minutes' (1320000 milliseconds) | * We set `scenario_time` to '''20 minutes''' (1200000 milliseconds), and `page_timeout` to '22 minutes' (1320000 milliseconds) | ||
** It's crucial that `page_timeout` exceed `scenario_time`; if not, measurement tests will fail/bail early | ** It's crucial that `page_timeout` exceed `scenario_time`; if not, measurement tests will fail/bail early | ||
* The Firefox Android app is started up | * [start] Power-use/battery-level measurements are taken, via: | ||
* adb shell dumpsys battery | |||
* The Firefox {Fenix, Fennec, GeckoView, Reference Browser} Android app is started up | |||
* Post-startup browser settle pause of 30 seconds | * Post-startup browser settle pause of 30 seconds | ||
* On Fennec only, a new browser tab is created (other Firefox apps use the single/existing tab) | * On Fennec only, a new browser tab is created (other Firefox apps use the single/existing tab) | ||
* Power-use/battery-level measurements are taken, via: | * [final] Power-use/battery-level measurements are taken, via: | ||
* adb shell dumpsys battery | * adb shell dumpsys battery | ||
* Raw power-use measurement data is listed in the perfherder-data.json/raptor.json artifacts | * Raw power-use measurement data is listed in the perfherder-data.json/raptor.json artifacts | ||