Run tests and components

Relevant for: GUI tests and components and API testing

When you run a test or component, OpenText Functional Testing performs the steps it contains. If you have defined test or component parameters, OpenText Functional Testing prompts you to enter values for them. When the run session is complete, OpenText Functional Testing displays a report detailing the results.

For details about running business process tests, see Manage BPT tests and flows.

You can run OpenText Functional Testing tests from a number of different places:

Running tests differs slightly when running GUI tests/components or API tests/components:

OpenText Functional Testing always runs a test or component from the first step, unless you specify otherwise. You can:

Run method Description
Run the entire test or component from the beginning OpenText Functional Testing runs each step, starting from the first step in the first action, in sequential order.
Run only a part of a test

You can run sections of a test using these commands:

  • Run from Action: Runs the test from the specified action to the end of the test.

  • Run to Action: Runs the test from the beginning of the test to a specific action.

  • Run from Step: Runs the test from a specified step to the end of the test.

  • Run to Step: Runs the test from the beginning of the test to the specified step.
Run an iteration of a single action (tests only)

Using the Run Current Action command, you can run a single iteration of an individual action.

If the action contains nested actions, OpenText Functional Testing runs the nested actions for the defined number of iterations.
Debug a section of a test or component

If you need to debug a section of your test, you can use the following commands to narrow down the scope of the debugging:

  • Debug from Step: Starts the run/debug session from a specified step.

  • Debug from Action: Starts the run/debug session from the first step of the selected action.

Make sure the application is open to the relevant section when using these commands.
Update your test or component to change test object descriptions

You can use the Update Run command to run the test in update mode, which enables you to update test object descriptions, or checkpoint values and Active Screen images/values (when running a test),

For additional details, see Maintain tests or components

Run a set of tests Using the Test Batch Runner, you can create a batch of tests and then run all of these tests together in a step.
Skip certain steps if necessary You can designate certain steps as optional, which enables OpenText Functional Testing to skip them if they fail.
Specify the number of iterations for a test or action (tests only)

If your test contains data parameters stored in the Global data sheet, by default OpenText Functional Testing runs an iteration for each row in the Global data sheet.

Likewise, if a test action references an individual action data sheet, OpenText Functional Testing by default runs an iteration of the action for each row in the Action data sheet.

In the Run Pane of the Test Settings dialog box or the Run tab of the Action Call Properties dialog box, you can specify whether to run one iteration, an iteration for each row, or a selected number of iterations.

Remote testing

If you run GUI tests on a remote machine, you can also run your GUI tests via the Windows Remote Desktop connection with a disconnected Remote Desktop Connection. For details, see Run a test from a remote computer.

Run mobile tests

Run mobile tests on multiple apps, devices, operating system, or run multiple tests in parallel. For details, see Run Mobile tests.

OpenText Functional Testing runs the test steps contained in the test flow in sequence, unless specified otherwise. You can:

Debug the test

If you have inserted breakpoints in your custom code or event handler code, OpenText Functional Testing pauses the test run to enable you to debug the code.

In order to use debugging, you must run the test in Debug mode. This option is set in the API Testing General pane of the Options Dialog Box.
Stop the test run if a checkpoint fails In the Test Settings tab for the test, you can instruct OpenText Functional Testing to stop a test run if a test fails.
Run a set of tests Using the Test Batch Runner, you can create a batch of tests and then run all of these tests together in a step.