Using test data is a simple way to inject dynamic data into your tests. Each item acts as a placeholder. When a test executes, it uses the value that corresponds to the data you inserted.
Rainforest supports several test data types. Read on for a brief summary of each. Use the links to learn more, including short setup videos and example use cases:
Static data allows you to share single values across multiple steps and tests. This is useful for information such as credit card numbers, URLs, and any other value you want to use repeatedly. Rather than keying in the value each time, you create static data and reuse it across your steps and tests. When you need to change the value that corresponds to the static data, you can do so easily; the value updates across all tests containing the placeholder. For more information, see Static Data.
Dynamic data allows you to define your own placeholders in a CSV file and upload them to Rainforest. Doing so allows you to assign each tester a unique value that you define. The most common use case is assigning login credentials for each test so your tests can execute in parallel in separate accounts. For more information, see Dynamic Data.
We’ve taken dynamic data a step further by creating environment-specific test data. If you require different login credentials per environment, this type of test data is your best option. For more information, see Conditional/Environmental Data.
These Rainforest-created placeholders generate random and discrete data, such as first name, email address, inbox, and Social Security number. For more information, see Built-In Data.
Use Rainforest’s pool of SMS numbers to test your app’s ability to send text messages. Then, use our SMS inbox placeholders to verify receipt of the SMS—all from within the web browser. No mobile device is needed. For more information, see SMS Test Data.
Note: If you’d like to purchase your own pool of dedicated SMS numbers, check out our Private SMS Numbers offering.
Marking test data as reusable allows more than one virtual machine to access it. This is useful when you are unable to create multiple data rows. Using this option will increase test execution time as the automation service waits for the test data to become available before kicking off the next test.
Visit one of the articles listed above to find out how to add and manage the test data types you need. To learn about adding test data to your test cases, see these articles:
Use test data to inject dynamic information into your test steps. You can create custom data to be used to meet the needs of various situations. Concatenate two or more different test data placeholders. This is useful when you want to create unique names for testing things such as sign-up pages. Doing so helps to ensure the test has a unique value to work with.
If you have any questions, reach out to us at [email protected].
Updated about 1 month ago