Rainforest Tests: Actions, Assertions and Embedded Tests

Rainforest Tests provide the ability to write tests that can be executed via Automation Service, Tester Community, or On-Premise Testers.


Rainforest vs. Rainforest Classic

Rainforest Automation and RFA are now Rainforest tests.

  • Rainforest Tests - Quickly capture UI element with screenshots
  • Rainforest Tests provide easy and efficient test writing for desktop applications. Test execution may be done via Automation Service, Tester Community or On-Premise Testers.

Plain English tests are now Rainforest Classic tests.

  • Rainforest Classic tests - Detail your test case line by line
  • Rainforest Classic tests allow you to write instructions via a free-form English testing writing interface. Tests may be run on desktop applications, mobile browsers, and mobile applications. Test execution is done via the Tester Community or On-Premise Testers.



Rainforest Tests are built on actions, assertions, and elements. Think of them as verbs and nouns.

Click (Action / Verb) on the Red button (Element / Noun)

  • Actions such as Click, Fill, and Navigate are used to mimic how a person would interact with the site.
  • In addition to actions, Rainforest needs to know what to take action on. This is referred to this as the Element or Target. These are items such as a button or text box.
  • When you combine an Action and an Element, you have created a step that can be executed by either the Automation Service or Tester Community.
  • Multiple steps that are used over and over may be grouped together into an Embedded test. More about this later.

The editor groups these to make it easier to find and use.

Embedded TestsEMBED



Actions provide direction on what interaction is required such as a Click on a button or Navigate to a URL.

Action Options

Action Options provide additional control over the action.

A Click can be done using the left, middle, or right mouse button. Navigate may be done via the current tab, a new tab, or an incognito tab.

Clicks on the UI Element
Default: left-mouse
Options: middle-mouse, right-mouse, and hold.

Note: Click and hold will require a number of seconds.
Close Tab
Closes current browser tab
Double Click
Double-clicks on the UI Element
Drag and drop
Drags and drops one UI element to another
Clicks into a text field and fills it with specified content

Combines Click and Type
into a single step.
Hovers over specified element
Navigates to specified URL
Default: current tab
Options: new tab, incognito tab
Press specified key or key combination
See Press section below
for more information
Refreshes the current page
Scrolls the page in a direction until a specified element is found.

Note: Up to 25 scrolls can happen with one scroll action. If a page is longer then two scroll actions may be needed.
Default: Down
Options: Up, Left, Right
Selects a specified item from a dropdown
Tester Instruction
An action for a human to complete

Note: test will need to be executed by the Tester Community if this step is used.
Types in the specified text one character at a time.
Waits for a specified number of seconds.
Note: This can be used if it is known that a page needs time to process a request or update




Press Sends a single key or key combination

Along with keys such as 'c', 'a', 'v', the following are also acceptable:
CapLock, Tab, ArrowDown, ArrowUp, ArrowLeft, ArrowRight, PageDown, PageUp, Escape, Home, End, Delete .

Backspace when in a text box, deletes one character from the cursor location.
Enter use Enter instead of Return.

NOTE: We have made it easy for you, just start typing in the key field and available options will show for selection!

The Modifier is an additional key that is used at the same time to modify the action. It is optional and should be left blank if not needed. Common modifiers are: Control, Alt, Tab, Shift such as Control + c to copy.

Command key can be used for MacOS.
Super can be used on Windows tests to act as the Windows key.

NOTE: Currently does not support three key
combinations such as Control + Shift + Delete.

New TabControlT
Open FileControlO
Focus Next(none)Tab
Focus PreviousShiftTab

Here's a demo of how it works:



Assertions are actions that confirm a specific behavior such as a page loading, an element being present or not or if a behavior has occurred.

Checks if a specified page has loaded.
Checks if an element of the UI is visible or not.
Default: visible
Option: not visible
Tester Confirmation
Ask a question to confirm behavior.
Any test that has a Tester Confirmation
a step may only be run by the Tester Community.



Alphabetically lists all the tests that can be embedded into the current test.

Any test created in Rainforest may be embedded into any other Rainforest test.
Embedding a test is beneficial for steps that are used in several tests, such as logging in, creating an account, etc.

See Embedded Tests for additional information.

NOTE: If you had previously used Custom Actions, those tests are available for use but are shown as Embedded Tests.

If you have any questions, please feel free to reach out to us at [email protected] or through Intercom!

Updated about a month ago

Rainforest Tests: Actions, Assertions and Embedded Tests

Rainforest Tests provide the ability to write tests that can be executed via Automation Service, Tester Community, or On-Premise Testers.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.