Visual Editor test steps are built on actions such as Click, Fill, and Navigate. These actions mimic how a person interacts with your site. Use actions combined with elements to create test steps. Group frequently-used multiple steps into an embedded test.
A step begins with an action. Depending on what the action requires, add combinations of options, elements, and values.
For example, Click requires an option such as left, right, middle, or hold. And you need to specify which element to click. Navigate requires a destination and an option for which browser tab to use, such as Current, New, or Incognito.
Actions represent an activity such as clicking a button or navigating to a URL.
Options provide additional control over an action. For example, you can further define a click by indicating the left, middle, or right mouse button; or you can click-and-hold. You can navigate to a URL in the Current tab, a New tab, or an Incognito tab.
Note: Not all actions have options.
Actions are broken into three sections and are listed alphabetically within each section to make them easy to find and use.
- Comment. Provides context and clarity for a step, group of steps, or test.
- Interact. A core group of actions that allow interaction with a site or application.
- Assert. Confirmation actions that ensure an application is in a specific state.
- Embed. Groups of test steps that are frequently run together.
Comment Action steps are plain-text test steps that don’t execute within a test. Instead, they provide an easy way to share information with other users who read the test. Using comments strategically lets you create tests that are clear and easy to understand so other users can review, debug, and update.
Provides information about the steps or test so others can more easily understand, debug, and update.
Comment Action Best Practices
- Be brief. Comments should be written so others can quickly skim and understand.
- Use freely but avoid line-by-line comments. Provide enough context so others can easily understand why the test was written that way.
- Avoid referring to items that might change. For example, don’t reference step numbers or other comments in the test directly.
Are Comment Actions Counted Against Usage?
No. Since these steps are “skipped over” in your previews and runs, they don’t count against your usage—and they don’t cost anything.
Clicks the Element.
Options: Middle Mouse, Right Mouse, and Hold
Note: Click-and-Hold requires the number of seconds.
Closes current browser tab.
Double-click the element.
Drag-and-drop one element to another.
Clicks into a text field and fills it with the specified content.
Combines Click and Type into a single step.
Hovers over the specified element.
Navigate to the specified URL.
Options: New tab, Incognito tab
Requires a value.
Press the specified key or key combination.
See Press Action Tips below for more information.
Refreshes the current page.
Scrolls the page in the specified direction until the element is located.
Options: Up, Left, Right
Note: You can execute up to 25 scrolls with a single scroll action.
Selects specified item from the dropdown.
An action for a human to complete.
Note: If this action is used, the test is executed by the Tester Community.
Types the specified text one character at a time.
Waits the specified number of seconds.
Note: Use this if a page requires an excessive amount of time to process a request or update.
Press sends a single key, or a key combination such as
Control + C. In addition to keys such as
V, the following are also available:
We made pressing keys easy. Start typing in the Key field, and the available options appear.
Superon a Windows VM translates to the
Superon a iOS VM translates to the
The modifier is an additional key you can apply to the action. Note that it’s optional and should be left blank if not needed. Common modifiers include:
Press Action Tips
Create Press actions that mimic the way you interact with your keyboard.
- When inside a text box,
Backspacedeletes one character starting at the cursor position.
- You can use
Superon Windows tests to act as the
- To zoom a window in or out, use
Note: Currently, Rainforest does not support three-key combinations such as
Assertions affirm a specific behavior, such as a page loading, an element being present or not, or whether the behavior occurred at all.
Checks whether an element is visible or not.
Option: Not visible
Ask a question to confirm a behavior.
Reusable Snippets are available for use within the current test. Reusable Snippets are alphabetically listed within the Snippets section.
Any test you created in Rainforest can be embedded into any other Rainforest test. Embedding a test is beneficial for frequently used steps, such as logging in or creating an account. For more information, see Reusable Snippets.
Note: If you previously used custom actions, they now show as embedded tests.
If you have any questions, reach out to us at [email protected].
Updated about 1 month ago