v33.0.0

Announcement: In the next major release we will remove all support for WebPageTest. If you still plan to use WebPageTest you can probaly still use the plugin for a while if your WebPageTest installation works.

Breaking

This is a breaking change if you use the compare plugin and do not set an id (--compare.id) for your test.

• If you auto generate the id for your compare test, this PR add browser, connectivity name and slug to the file name where the compare metrics is stored #4083.

Added

• Updated to Browsertime 21.2.0 that adds a new way to stop your measureemnts if your navigation fails measure.stopAsError(failureMessage, optionalURL). Perfect to use in a try/catch.
• Use darkmode for result HTML by adding --html.darkMode, thank you petemyron for PR #4081.

Fixed

• Update co2.js to 0.14.2 #4074
• More solid error handling if one page fail in scripting. This fixes so that the HTML for the rest of pages should be generated #4079.
• Remove console.errors of errors (they have already been reported in the log) #4080.
• Fix automatically switch to Throttle as engine on Mac and Linux if you add -c THROTTLING#4082.

v32.2.0

Added

• Chrome and Chromedriver 121 in the Docker container #4069.
• Browsertime 21.1.0 #4070.

v32.1.0...v32.2.0

v32.1.0

Added

• Updated the WebPageReplay version in the Docker container #4067.
• Firefox 122 in the Docker container #4068.

v32.0.0...v32.1.0

v32.0.0

Breaking change

• If you use the compare plugin (--compare.saveBaseline) you need to remove your old baseline when you upgrade. The reason is that the original implementation was very narrow to some Browsertime metrics. The new version will be able to show more information (more metrics) between the baseline and the current test. This version allo disables comparing the CDP performance metrics, making the compare page easier to understand #4064.

v31.2.1...v32.0.0

v31.2.1

Fixed

• Another fix for --budget.suppressExitCode hopefully it works better this time #4065.

v31.2.0...v31.2.1

v31.2.0

Fixed

• There was bug that caused budget.suppressExitCode to fail that I introduced and reported in #4062. It's fixed in #4063.

Added

• Collect statstics about how the page is built between runs. You can see these metrics on the "side by side"-page #4061.

v31.1.1...v31.2.0

v31.1.1

Fixed

• When displaying interaction to next paint, there where some copy/paste from largest contentful paint that sometimes broke the HTML (my fault). Fixed in #4042.

v31.1.0...v31.1.1

v31.1.0

We updated the scripting documentation to be generated directly from Browsertime (using JSDoc). This makes the documentation so much easier to navigate. It's not 100% perfect yet so please feel free to send PRs with updates :)

The new version of Browsertime also adds code completion/IntelliSense support. Read here on how to set it up. Make sure to start your scripting like this:

/**
 * @param {import('browsertime').BrowsertimeContext} context
 * @param {import('browsertime').BrowsertimeCommands} commands
 */
export default async function (context, commands) { 
 
};

Added

• Update to Browsertime 21.0.0:
  • Upgraded to Geckodriver 0.34.0 #2049.
  • Collect CPU consumption for Firefox. Turn that on with --firefox.powerConsumption true and including power as a geckoProfilerParams.features #2046.
  • Added more commands for mouse click on text #2054.
  • Updated AndroidCommand so you can run shell on your Android device as root #2055.
  • If you mark a test as failure, the exit code from Browsertime will be 1. If the exitCode is set in scripting, we use that and will not change that #2057.
  • Generate documentation for scripting using JSDoc #2059.
  • Make it easy to use Seleniums action API. Get access to the new command using commands.action.getActions() and chain the action. #2061
  • Make sure the visual metrics files are inlcuded in the Docker file #2053.
  • Removing QVH from the npm package (used for iPhone video recording but not working) #2051
  • Removing visual metrics test images from the npm package #2050.
  • Removed the Chromedriver fix that was needed when Chrome for testing broke testing on Chrome :D #2045.
  • Refactor of commands/context object to prepare for supporting JSDoc and a little TypeScript to add code completion/IntelliSense in editors #2047.
  • Updated documentation for scripting with better JSDoc #204.
  • The code for getting Interaction to next paint was broken. This PR fixes it, make the code cleaner and gives more attribution #2060.
• If you use process.exitCode in your scripting, it will be respected by sitespeed.io and exit with that exit code #4044.

Fixed

• If a run is markedAsFailure in your Browsertime script, sitespeed.io exits with an error code #4047.

v31.0.1

Fixed

• Hopefully removing "rsd" metrics in InfluxDB see #4039.
• Fix showing sustainable metrics in pages page #4042.

v31.0.0...v31.0.1

v31.0.0

Breaking

• Updated to Browsertime 20. The new version of Browsertime renames --userTimingWhitelist to --userTimingAllowList so if you use that functionality you need to change the name before you upgrade!

Fixed

• The new version of Browsertime also fix the bug in Firefox 121 on Mac so you can start it.

v30.11.0...v31.0.0