Automate Scrolling in Scenario Editor

Automate Scrolling in Scenario Editor
Use scrolling when the target element or content is not currently visible in the browser viewport. Prefer scrolling to a stable element or section over relying on pixel-only movements.
Recommended workflow
Identify the element or section the scenario needs to reach.
Scroll until the target is visible and stable.
Use a conditional wait if content loads asynchronously after scrolling.
Perform the validation or action once the target is ready.
Good practices
Avoid scroll steps that depend on a specific screen size unless that is the test objective.
Validate the target element after scrolling before clicking or typing.
Document mobile or responsive behavior separately when scrolling differs by viewport.
Last updated: September 9, 2026