Changelog 2023.11

Browser Console Logs in Traces

Browser Bot traces now include logs from the bot’s browser console. This can sometimes be helpful if a page didn’t load correctly due to an error on the page.

Other Improvements & Bug Fixes

• Improved cache behavior in the Chrome browsers used by Browser Bots.
• Added a filter to the Total Time Spent table to calculate aggregates (total, average, and request count) based on a subset of data.
• Adjusted the automatic test advice section to reduce confusion between functional and performance errors.
• Addressed a global state issue that sometimes caused old versions of scripts to persist in the UI if someone else on your team had modified them.
• Fixed a bug with trace filtering treating blank values as matches instead of non-matches.
• Improved the progress indicator so it doesn’t block navigation to other pages.
• Cleaned up live test sidebar text wrapping.

Further Reading

Browser console logs are something web developers rely on frequently when debugging pages, and with this release they became available inside your load test traces too. If a page fails to load or behaves unexpectedly during a test, the console logs can reveal JavaScript errors, failed resource loads, or other client-side issues that wouldn’t show up in network-level traces alone. This is particularly useful for single-page applications where much of the behavior happens in the browser.

The cache improvements are also worth noting – realistic cache behavior matters because real users have some resources cached after their first page load, and your browser scripts should reflect that.