Test Data & Special Testing Scenarios

Overview

Tests become more powerful and more maintainable when they use real, representative data instead of hardcoded values. Rainforest gives you several ways to inject data into your tests at run time, so your tests stay flexible without requiring constant updates.

Test Data

Test data in Rainforest works through placeholders. You add a placeholder to a test step, and when the test runs, Rainforest replaces it with the corresponding value. There are four types of test data, each suited to different situations. Static Data stores a single, unchanging value that you want to reuse across multiple tests. A good example is a test credit card number or a staging URL. When you need to update the value, you change it once in your settings and it updates everywhere. Dynamic Data lets you define a list of values in a CSV file and upload them to Rainforest. Each test run receives a unique row, which is most useful for login credentials. If multiple tests are running in parallel, each one gets its own set of credentials and avoids shared state issues. When calculating how many rows you need, account for the number of tests, browsers, retries, and automation agents in your run. Built-In Data generates random values automatically without any setup. Rainforest provides placeholders for names, email addresses, phone numbers, addresses, dates, and more. Use these anywhere you need realistic but throwaway data, like signup forms or profile fields. Conditional/Environmental Data is an extension of dynamic data that lets you define different values per environment. If your staging and production environments use different login credentials, conditional data handles that automatically without requiring separate tests.

SMS Test Data

Rainforest provides a pool of SMS numbers you can use to test workflows that involve sending or receiving text messages, such as two-factor authentication via SMS. Use the SMS inbox placeholder to verify receipt of a message from within the browser without needing a physical device. If your plan includes dedicated numbers, private SMS numbers give you a stable pool that isn't shared with other accounts.

Special Testing Scenarios

Some workflows require specific approaches that go beyond standard step authoring.

Two-Factor Authentication can be tested using Rainforest's built-in SMS test data or by using a test account configured with a static OTP that doesn't change between runs.

Chrome Extensions require the extension to be installed on the virtual machine before the test runs. Rainforest supports this through a download step at the start of the test.

Desktop Application Installation can be tested by downloading the installer to the Rainforest VM and walking through the installation flow as a user would.

Multiple Account Interactions allow you to test scenarios that require two users to interact simultaneously, such as sending a message from one account and receiving it in another. Rainforest handles this by running concurrent tests with separate dynamic data rows.

**Storing Values Generated ** during a run lets you capture a value produced mid-test, such as an order number or confirmation code, and reference it in a later step within the same run.