Scroll the viewport to the top or bottom of the page
Modern web pages frequently include content that only appears after scrolling. This can include infinite lists, lazy-loaded elements, sticky headers, or interactive sections that depend on scroll position. The Scroll to Edge step allows your test to programmatically scroll the viewport all the way to either the top or the bottom of the current page, giving your automation the ability to reach content that is not visible on initial load.
By automating scroll behavior, you ensure that your tests interact with the page the same way a real user would—discovering content as it becomes visible and triggering reactions that only occur after scrolling.
Why scrolling matters in automated tests
Many applications rely on scrolling to:
Reveal additional content or navigation
Trigger animations or content loading
Load more items in infinite lists
Expose footers, call-to-action buttons, or forms
Activate lazy-loaded images or scripts
If your automation does not scroll, it may miss critical elements or paths entirely. The Scroll to Edge step lets you reach those parts of the page reliably.
How it works
With this step you can scroll to:
Top of the page — useful to reset the viewport before interactions
Bottom of the page — useful to view or interact with content that appears only at the end
You choose the direction based on what your flow needs next.
For example:
After loading a long article, scroll to bottom to confirm the footer content
After adding items to a list, scroll to top to assert a “Back to top” button appears
Before capturing a visual regression snapshot, scroll to reveal sections that matter
During form validation, scroll to a field that is not immediately visible
This helps ensure your test interacts with the correct content.
Combine scrolling with other steps
The Scroll to Edge step is often paired with:
Touch — to interact with elements only visible after scrolling
Check Text — to assert content that was hidden before
Check Value — to confirm field contents near the bottom of the page
Visual regression — to capture a snapshot of the fully visible page
Wait for Element — to ensure newly revealed elements have loaded
By combining scrolling with these actions, your automation can cover deep, content-rich pages comprehensively.
Simulate realistic user interaction
Users often scroll to explore content, not just to view what’s immediately visible. Including scroll steps makes your automated flows reflect real user behaviour.
This is especially important for:
Blogs and documentation pages
Product lists and catalogues
Dashboards with expandable content
Long-form checkout pages
Footers with critical links or disclosures
Automated scrolling ensures that elements only visible after user exploration are included in your coverage.
Reliable and predictable scroll behaviour
Because this step explicitly controls scroll position, your tests do not rely on implicit timing or other indirect signals. Scrolling to an edge is deterministic, improving test stability and reducing flakiness.
When your automation behaves like a user who explores the entire page, your coverage becomes richer, more representative, and better aligned with real-world usage patterns.