Documentation

Environment Specific Execution

To enhance test execution across different environments (e.g., QA, Staging, Production), HuLoop allows you to create multiple test data sets with the same name but mapped to different environments. This avoids the need to manually associate and disassociate test data when switching between environments.

• Using Test Data Across Environments
• Switching Environments for Test Data Execution

Using Test Data Across Environments

Example Scenario:

Suppose you have test data named User Details in the QA environment, containing local user details. Now, you need to use the same test data in the Production environment, but with production-specific user details. Instead of modifying or re-associating the test data manually each time, you can create another User Details test data set for Production without setting it as the default.

Steps to Configure:

1. Navigate to Manage Test Data and create new Test Data.
2. Enter the same Test Data Name as the existing one (e.g., User Details).
3. In the Environment Name field, enter the environment name (e.g., Production).
4. Keep Execution Mode as Sequential.
5. Define the test data values specific to the chosen environment.
6. Click Save.

At this point, the Manage Test Data page will display multiple test data sets with the same name but mapped to different environments, as shown below:

Note: There should always be one test data set with the default environment. When associating test data with a case or suite, HuLoop will pick the test data that has the default environment assigned. However, during execution, you can switch the environment to use a different test data set based on your needs.

Switching Environments for Test Data Execution

By default, when you execute a test case, HuLoop picks the test data associated with the default environment. However, you can override this behavior and select a different environment’s test data.

Steps to Change the Test Data Environment:

1. Go to your automation in which you have the Test Data.
2. Open Settings > Automation Settings. (Click the Settings icon. By default, it will open the Automation Settings page.)

3. Locate data_setting_name in the list.
4. By default, its value is set to default. You can edit it by clicking the icon against it.

5. Change the value from default to the environment name you specified when creating the test data (e.g., Production).

6. Click Save.

When automation runs it will pick the test data mapped with Production environment.

Notes:

• Test data is always associated with the default environment by default. You can change the execution environment dynamically without re-associating data.
• The test data file name must remain the same across environments. This ensures seamless execution and avoids the need for repetitive association/disassociation.