How to Change Environments

How to test with different environments in the Visual Editor.

When creating a Rainforest test with the Visual EditorVisual Editor - A tool that allows you to write tests using precise browser interactions with a live preview. Tests created with the Visual Editor (VE) run using either the Automation Service or Tester Community. (VE), tests run in the default environment for the selected site. You might need to preview a test in a different environment. Maybe the appropriate code isn’t in the current environment yet, or you want to test something in an environment where tests are not normally run. For more information, see Create a new environment in our API Reference.

Changing Your Environment

  1. Open the Visual Editor test.
  2. Select the URL in Step 1 (Start at).
  3. In the Starting URLmodal, select the new environment.
  4. Click the Submit button.

The Start at URL is updated with the new environment URL. In addition, Environmental ID and environmental variables are updated.

Changing environments.Changing environments.

Changing environments.

🚧

The Updated Environment Is Not Saved

Any changes you make to the environment are only available for the current editing session. Once you exit the test, the environment reverts to its default. However, if you save your test, all edits are preserved, except for the environment.

📘

Embedded Tests Open in the Parent Environment

If you open an embedded test when the environment of its parent has been updated, the embedded test inherits the new environment.

Reviewing a Test from a Run

When you access a test from a run, it uses the environment you set. For example, if the default environment is Staging, but you ran the test in production, the test opens with Step 1 (Start at) using the production URL, environmental IDs, and variables.


If you have any questions, reach out to us at [email protected] or via the chat bubble below.


Did this page help you?