Best Practices

Optimize for a single browser.

Run Visual Editor tests with automation on the same browser the test was created on. Automated tests rely on screenshots, resulting in tests optimized for a single browser. You can still run cross-platform tests using our Tester Community.

Follow screenshot size best practices.

Providing relevant screenshots is the best way to ensure accurate results. Including a screenshot that’s too large could result in unexpected failures. Conversely, screenshots that are too small might miss an essential part of the screen. For more tips on taking the best screenshots visit our Screenshot Best Practices article.

Use the Target Indicator

When creating a screenshot, Rainforest automatically places a target indicator in the center. This is where an action such as Click takes place. However, sometimes the action occurs somewhere else on the screen. Adjust the target as required.

In the following example, the target needs to be moved to the left. As a result, “Where” is clicked instead of “going.”

Follow test data best practices.

Though you can use test data in Visual Editor tests, validation is limited to static data. For more information on Test Data, see Using Test Data.

Reusable Snippets

Visual Editor tests support reusable snippets. For more information, see Visual Editor reusable snippets.

Name elements appropriately.

Naming elements is a requirement. Use names that clarify the step’s action. Doing so is useful when reviewing and updating the test. “Submit - login page” is more precise than “Submit.”

Scrolling Long Pages

Utilize the Scroll function if you need to view a part of the page that isn’t at the top. However, for long pages, use the browser’s built-in Find function instead to locate the element on the page. Then, perform the action you want on it.

1. Use the Press Key function for Control + F
2. Use Type to provide what you want to search for.

If you have any questions, reach out to us at[email protected].