Execution overview

Functional Test Execution enables you to execute UFT One web tests, mobile tests, and codeless tests in OpenText’s cloud environment. You select the testing tool and browser versions you’d like to test with, add your tests to a test suite, and Execution will run your tests in the cloud.

Workflow

Provide ValueEdge with access to the Git repository where your UFT One scripts are stored. You then add the scripts to test suites that are executed in a UFT One machine hosted in OpenText’s cloud environment. You can also use these scripts as units in Model-Based Testing.

A scheduling mechanism enables you to automatically run test suites according to your preferred schedule (nightly, weekly, and so on).

The following is the general workflow:

  1. Configure a cloud runner to connect your Git repository with ValueEdge. For details, see Enable cloud execution.

  2. Create a test suite and add tests using the Tests tab. For details, see Create and schedule a test suite.

  3. Create schedules based on your operational needs, using the Schedules tab. For details, see Create schedules.

  4. Track schedule runs and execution results using the Scheduled Runs tab. For details, see Monitor test execution.

  5. Use the Defects tab to manage defects related to your tests. For details, see Defects.

Note: To enable execution of UFT One automated tests on mobile devices, please contact MFI-mbt-swat-ww@opentext.com.

Back to top

Execution Overview tab

When you first open the Execution module, the Overview tab is displayed. The following widgets are displayed by default:

Widget Description
CI Cloud Status Indicates if the OpenText cloud engine is available for test execution. If it is down, contact Support.
Cloud Runners Displays cloud runner status. For details on creating cloud runners, see Enable cloud execution.
Current License Usage Displays the number of Test Execution concurrent-run licenses in use, out of the total available licenses.

Users with admin permissions can drill down to corresponding configuration areas. For example, if you have permissions to create a cloud runner you can drill down from the widget to the related Settings area.

For details on customizing widgets, see Dashboard.

Test run status widgets

You can add the following widgets to track test run statuses:

Widget Description Configuration
Most recent status per schedule Shows results of the latest run, per schedule, for multiple schedules. After adding the widget, select multiple schedules from the widget configuration settings.
Schedule over time Shows run results of a selected schedule over time. After adding the widget, select a schedule from the widget configuration settings and filter by release, sprint, or milestone.

Back to top

Working with codeless tests

Functional Test Execution enables you to schedule and run codeless tests in the cloud. For details on creating codeless tests with the FT Design sub-module, see Functional Test Design Help Center.

To run a standalone codeless test:

  1. In the Functional Test module's Execution page , open the codeless test. The Test runner field is automatically set to Codeless Runner.

  2. Optionally add parameters and data sets to your test:

    1. Select the Parameters tab and click + Codeless Test Parameter. Optionally, assign a default value.

    2. In the Data Sets tab, add values for each of the parameters. When you run your test with a data set, the script runs iteratively, using one row of parameter values from the data set for each iteration.

To run a test suite that contains codeless tests:

  1. Prepare your codeless tests as described above. Optionally, add parameters and data sets.
  2. Create a test suite that will contain the codeless tests.
  3. Click + Codeless Test to add tests to the test suite. The Test runner field for the codeless tests is automatically set to Codeless Runner.

  4. In the Functional Test module's Execution page, open the test suite containing the codeless tests.

  5. Open the test suite details, and in the Test execution configuration section, select a machine template that contains Codeless. For details, see Create a test suite.
  6. Run the test suite. If your codeless test uses parameters, it runs iteratively using one row of parameter values from the data set for each iteration.

Back to top

License usage

Test suite runs are executed based on Function Test Execution license availability. If there aren't enough available licenses to run a test suite, the run will be queued and executed when enough licenses are available.

The following details apply:

  • If you select parallel execution for a test suite, the test suite will run according to its schedule and when enough licenses are available to run the tests in parallel.

  • If you select serial execution for a test suite, the test suite uses only one license.

  • If you select to run an ad hoc test suite, the test suite will run according to priority versus scheduled runs and according to license availability.

Back to top

Advantages of Functional Test Execution

Working with Functional Test Execution provides you with the following advantages:

  • Unattended test execution can be scheduled to run once at a specific time, or to run periodically at specific intervals. You can also execute tests on-demand.

  • Execution dynamically allocates UFT One hosts in OpenText’s cloud environment, enabling to run several tests in parallel. Your license determines the maximum number of tests you can run at once.

  • A centralized control center enables you to view all your scheduled jobs, see what is currently running, and view execution status and reports of completed tests in one location.

To learn more about the ValueEdge solution, see ValueEdge.

Back to top

See also: