Configure your parallel test runs using a UI

Use the Parallel Runner graphical user interface to configure your parallel test runs. You can also define conditions that synchronize between test runs.

In this topic:

Overview

OpenText Functional Testing's Parallel Runner UI provides a visual way to configure a parallel test run plan and create a JSON-formatted configuration file. You can specify multiple types of tests to run in parallel and define the environment, data table, and parameters to use for each test run.

You can open the Parallel Runner UI from the Windows Start menu or from OpenText Functional Testing's Tools menu.

Back to top

Configure your parallel test run

Perform the following steps to configure your parallel test run:

To configure your parallel test run:

1. Open the OpenText Functional Testing Parallel Runner UI.

2. Define test run information, including the ID, type, environment information, data table, and parameters for each test run.

   For details, see Define the ID, type, environment, data table, and parameters for each test run.

3. Define conditions to synchronize between test runs.

   For details, see Use conditions to synchronize your parallel run.

4. Click the icon in the bottom-left corner to define a path for saving the parallel test report.

5. Click the icon in the bottom-left corner to specify a title for the test report.

6. Click Save to save your configuration to a .json file that you can use in a command line for parallel testing.

   For information about how to start testing in parallel by referencing a .json file from a command line, see Step 2 in Manually create a .json file to define test run information.

   Note: You can drag and drop an existing .json configuration file to the Parallel Runner UI to modify your test run configuration.

7. To start your parallel test run, click the Run button in the bottom-right corner.

   You can click the gear icon to select whether to open the report during the test run and define the interval for refreshing the report.

8. To stop parallel execution, press CTRL+C on the keyboard.

   • Any test with a status of Running or Pending, indicating that it has not yet finished, will stop immediately.

   • No run results are generated for these canceled tests.

Back to top

Define the ID, type, environment, data table, and parameters for each test run

Define the following information for each test run in the Parallel Runner UI:

Configuration Item	Description
ID	The ID of a test. Click the ID column of each row and enter an ID. This ID is unique and useful when you specify conditions for each test run.
Test Location	The location of a test. Click the Test Location column of each row, and then click the folder icon to select the test file.
Test Type	The test type, including GUI-Web Test, GUI-Mobile Test, GUI-Java Test, and API Test. Click the Test Type column of each row and specify the type for each test.
Environment	This is mandatory if you set Test Type to GUI-Web Test or GUI-Mobile Test. If you set Test Type to GUI-Web Test, specify the browser type. If you set Test Type to GUI-Mobile Test, specify the device ID or device capability information, including the manufacturer, OS type, model, and OS version. Click View Details to collapse the Device Details section and configure the ID or device capability information.
Data Table	If your test uses a data table, click the Data Table column of each row, and then click the folder icon to select the corresponding data table.
Test Parameters	Click View Details to collapse the Device Details section and define test parameters. Data types Number, Boolean, and String are supported. To define a Number type value, enter the number (supported range: -2,147,483,648 to 2,147,483,647). To define a Boolean type value, enter True or False. To define a String type value, use straight double quote (""), such as "1" or "True".
Run Name	Specify a test run name for each test.

Back to top

Use conditions to synchronize your parallel run

To synchronize and control your parallel run, you can create dependencies between test runs and control the start time of the runs.

You can create the following types of conditions: 

• Simple conditions, which contain one or more wait statements.
• Combined conditions, which contain multiple conditions and an AND/OR operator, which specifies whether all conditions must be met.

To configure conditions for a test run:

1. In a row, click View Details to collapse the Conditions section.

2. Specify the condition syntax.

   • Select Global after Wait, and specify the time to wait before starting the test run.

   • Select a test ID after Wait, and specify the status to reach by the specified run before starting the test run, or specify the time to wait before starting the test run.

3. Click the icon to add the operator. You can add one of the following operator:

   • AND. All of the conditions following the operator must be met before the test run begins.
   • OR. The test run begins as soon as one of the conditions following the operator is met.

Back to top

See also:

• Run tests in parallel
• Run tests in parallel using a command line
• Known issues - Run sessions
• Testing with Jenkins