Changelog 2024.03

Script Logs in Traces

Traces in a load test or a load test report now include the bot’s script logs up to that point in the iteration. These logs will be familiar if you’ve spent time playing scripts in the script editor. Now the same script logs are available when you run a load test, in INFO traces (for Bot 0 in each bot group) and in ERROR traces (for any bot that has an error).

Having access to the bot’s logs will make it easier to understand and debug many types of errors that occur in a load test.

Other Improvements & Bug Fixes

• Updated the billing checkout flow to handle 3D Secure payment flows.
• Fixed a bug with frame selectors that caused ambiguity when multiple frames matched the first part of the selector.
• Improved memory handling on the cloud engines.
• Fixed a bug with script previews not counting Include steps in the step count.
• Improved test shutdown behavior in rare situations where the browser process dies.

Further Reading

If you’ve used the script editor’s playback feature, you’re probably familiar with the step-by-step logs that show what the bot is doing – navigating to a page, clicking a button, waiting for an element, and so on. Previously, those logs were only available in the editor. Now they show up in your load test traces too, which bridges the gap between script debugging and full-scale test debugging. When a bot hits an error during a load test, you can open the trace and see exactly what the script was doing leading up to the failure, just like you would in the editor. This is especially handy for browser scripts where timing and page state can vary under load. For more on working with traces and test reports, see analyzing test results.