Check element has not moved
The Check element has not moved step allows you to detect positional differences between the current run and a stored control.
Layout stability is critical for usability, accessibility, and trust. Small positional shifts can break designs, hide key information, or disrupt user journeys. This step verifies that an element remains in the same position across runs, helping you catch unintended layout changes early.
Detect layout regressions automatically
Modern applications change frequently. New banners, updated components, third-party scripts, and styling tweaks can all cause subtle layout shifts.
By comparing an element’s position against a control, DoesQA can:
Detect unexpected movement
Highlight visual instability
Protect critical UI elements
Prevent accidental design regressions
This is particularly valuable for navigation bars, call-to-action buttons, checkout totals, headers, footers, and key promotional areas.
Stronger than visual regression alone
While full visual regression is powerful, sometimes you only care about the position of specific elements.
Element position checks allow you to:
Focus on critical components
Avoid false positives caused by dynamic content
Validate layout structure without snapshotting the entire page
Monitor high-risk UI regions with precision
This gives you targeted layout validation without increasing maintenance.
Practical use cases
Checking element position is useful when:
Protecting fixed headers and sticky navigation
Ensuring checkout totals remain visible
Preventing overlapping components
Guarding against layout shifts from ads or dynamic content
Validating responsive behaviour across browsers and devices
It is especially powerful when paired with cross-browser testing, simulated devices, and visual regression to build layered confidence in your UI.
Maintain design integrity at scale
As your test coverage grows, automated layout validation becomes essential. Element position checks provide a lightweight but effective way to ensure your design remains stable between releases.
Use it to protect key UI components and catch subtle regressions before your users ever notice them.