Handling UI actions
Special instructions for handling certain UI actions
When creating a test, there will be steps that require interaction with the user interface (UI). Not all UI actions are created equal. Web pages are increasingly adding new capabilities that challenge most record/playback tools. Recording clicks and entering text into fields is easy, but other UI actions can be more difficult to track.
This section is devoted to making sure those more challenging UI actions like auto-scroll and drag and drop are properly recorded and represented in the visual test editor.
Advanced UI Actions
Below are some of the more advanced UI actions you can add to your test.
| Action | Description |
|---|---|
| Scroll | Add a step to your test when you want the test to scroll to a specific location or element of a page. |
| Auto Scroll | Control if the test should automatically scroll to a page element if the element is initially outside the viewport. |
| Drag & Drop Step | Add a step to your test that records a “drag and drop” action, such as a user dragging an image to an upload section or adding an element to a workspace in a visual editor. |
| Hover Step | Add a step to your test that records a hover action, such as a user hovering over a menu, tooltip, or button. |
| Navigation Step | Add a step to your test when you want the test to navigate to another page. |
| Refresh Page | Add a step to your test when you want the test to refresh the page. |
Updated almost 2 years ago
What’s Next
UI actions