v17.9.0

Added

• New command to start geckoprofiling when scripting using Firefox. Thank you KS for PR #1934. This is probably only something you need if you work at Mozilla. There's also a follow PR #1940 that fixes some of the issues I've been wanted to fix with the Geckoprofiler code.

• Use --enableProfileRun to make one extra run where metrics aren't collected but Geckoprofiler or Chromes timeline log is turned on. This useful if you are worrying about the trace causing overhead, but you still wan trace from the test/journey. It's a little rough at the moment so it will a follow up in the future #1943.

Fixed

• Bump Chrome remote interface and execa #1941.

v17.8.1

• Bidi HAR 0.0.10 (#1939) 16bb3fd

v17.8.0...v17.8.1

v17.8.0

Fixed

• Upgraded to Firefox HAR 0.0.8 #1937.

Added

• Upgraded to Firefox 112 in the Docker container.

v17.8.0-beta.1...v17.8.0

v17.7.0

• Edge/Edgedriver 112 (#1935) bf1f95b

v17.6.0...v17.7.0

v17.6.0

Fixed

• Increased the default wait time from 2 to 5 seconds when a element a clicked and the page complete check runs #1931

Added

• Upgraded to Chrome/Chromedriver 112 in the Docker container #1932.
• If you use --headless Chrome will use the new headless switch #1933.

v17.5.0...v17.6.0

v17.5.0

Added

• There's a new better way to get the HAR from Firefox using WebDriver BiDi network events. Thank you Julian Descottes and others at Mozilla that made this happen! With the new version we hope to see less overhead getting the HAR + it works on Firefox on Android #1918. You can turn it on with --firefox.bidihar.
• Updated to Geckodriver 0.33 #1928.

Fixed

• Fixed the interaction to next paint error message that started to appear in latest Chrome #1924.
• Safer check for getting last meaningful paint #1927

v17.5.0-beta4...v17.5.0

v17.4.0

Added

• Log the CPU benchmark metric to the console. This is useful (at least for me) when debugging instances with a lot of instability. #1920.
• In Chrome 111 some metrics become more instable when running on host with limited CPU. This change also exists in 112 beta. However we where missing out on a couple of command line magic to disable features in Chrome, this fixes that #1921.

v17.3.0...v17.4.0

v17.3.0

Fixed

• Bumped Selenium-webdriver to 4.8.2 #1916.

Added

• On Linux you can use taskset to assing FFMPEG to specific CPUs using --videoParams.taskset "0,5,7,9-11" . It will start FFMPEG with taskset -c <CPUS> to pin FFMPG to specific CPU(s). Specify a numerical list of processors. The list may contain multiple items, separated by comma, and ranges. For example, "0,5,7,9-11". Use it together with isolcpus. Added in #1917.

• If you use a rooted Samsung A51 you can now choose the CPU speed (min/middle/max) using --android.pinCPUSpeed min|middle|max #1915.

v17.2.1...v17.3.0

v17.2.1

Fixed

• Bumped Geckodriver to 0.32.2 and Edgedriver to 111.

v17.2.0...v17.2.1

v17.2.0

Added

• Updated Chrome, Chromedriver, Edge and Firefox to 111.

v17.1.1...v17.2.0