Changelog 2024.11

Scripting & Script Recording Improvements

Following up on the major update to script recording from October, we’ve further refined the way the script recorder determines whether a hover event has significance. This makes it easier to record important hover events in your script, such as when you hover to expand a CSS menu, without recording too many unimportant hover steps.

There are also a handful of UI improvements to the script editor itself. For instance, you can now hover on a step to reveal an Add button that makes it easier to add an adjacent step. Also, the tools to the right of a step now only appear when a step is hovered.

Other Improvements & Bug Fixes

• Fixed a bug that caused Browser Bots to fail ungracefully when a Wait For step timed out.
• Improved trace ingestion throughput for large clusters.
• Improved syntax highlighting UI responsiveness.
• Fixed a minor usability issue with the code block editing dirty state.
• Changed the default size of the modal dialog when viewing a script in a test report.
• Adjusted API rate limits.
• Fixed a potential resource leak with Chrome browser processes that affected long-running engines.

Further Reading

Script recording is one of the fastest ways to create a protocol script or a browser script in Loadster.

You install the Loadster Recorder browser extension, hit Record, and interact with your site in a new tab. The Recorder captures your clicks, typing, navigation, and other actions as script steps.

Hover detection is a tricky part of this process because you hover over things constantly as you move around a page, but only some hovers actually matter (like expanding a dropdown menu or triggering a tooltip). These improvements help the Recorder better distinguish between meaningful hovers and incidental mouse movement, so you end up with a cleaner script that needs less manual editing afterward. The new Add button in the script editor also makes it easier to insert steps at specific positions when you need to tweak things by hand.