Run tests

Run your tests locally or remotely, in parallel or in sequence, manually or using a CI server.

OpenText Functional Testing for Developers tests can be run using any of the supported licenses, including the UFT Runtime license.

Run your test

To run your tests locally, you compile your project, and then use either your testing framework's runner, such as NUnit or JUnit, to run your compiled .dll or .jar, or any other relevant runner.

If you are working with the UFT Developer MSTest template, you can run your tests from within Visual Studio.

If you are working with the UFT Developer NUnit/NUnit 3 template:

  • To run tests directly from Visual Studio, you must first install the NUnit Test Adapter extension NUnit 2.6.x or NUnit 3.x.

  • When running OpenText Functional Testing for Developers tests using the NUnit runner, make sure the Reload when test assembly changes option is selected. (NUnit Settings > Test Loader > Assembly Reload)

To run the test using Maven, run mvn test –P leanft-tests.

For Selenium projects, see the Selenium documentation.

During test design, you can run your tests in Android Studio.

To run your test using gradle, open a command line and run the following command from the project folder:

gradle UFTDeveloperTest

Run your tests using Jasmine, Mocha or another JavaScript unit testing framework.

Note:  

  • When you run a test based on an OpenText Functional Testing for Developers template, the inherited UnitTestClassBase launches the runtime engine so that the test can interact with your application during the run.

  • If you are working with your own C# or Java framework, or with JavaScript, you must use SDK.Init to enable communications:

Back to top

Run multiple tests in parallel on one machine

Save testing time by running multiple tests, or a single test with multiple data sets, in parallel on the same host machine.

When using a seat license, you can run up to four tests in parallel (different tests or the same test with different run data).

When using concurrent licenses, additional licenses are dynamically consumed, each enabling four parallel test runs. The maximum number of licenses to consume is defined in the runtime engine settings.

Running four test operations

Run parallel testing on:

  • Native and hybrid mobile applications

  • SAPUI5-based applications

  • Web applications

Create and run your tests in a unit testing framework that supports running tests in parallel. OpenText Functional Testing for Developers supports TestNG and NUnit 3, but you can also use any custom framework that launches tests in parallel.

Tip: To minimize performance issues when testing mobile applications, lock each device once for all tests. To do this, lock the device at the beginning of the class running your tests and not before each test.

For details, see Run tests in parallel

Back to top

Run tests remotely

You can run tests from your local computer, even if the application you want to test is located on a remote computer. This requires adjusting settings for your test, configuring the runtime engine settings on the remote computer, and in most cases, setting up secure communications between the two computers.

For details, see Run tests remotely.

Back to top

Run multiple tests using a grid configuration

Use the OpenText Functional Testing for Developers grid to run the same test operations on different environments by changing the parameters that describe the required environment. You can achieve distributed parallel test running, by running all of your tests on the grid, locally or remotely, and letting the grid allocate nodes for each test run, as needed.

For details, see Use a grid configuration.

Back to top

Run tests in ALM

You can use ALM tracking and traceability features to manage automated tests and business components.

For details, see Application Lifecycle Management (ALM).

Back to top

Add tests into the continuous integration system

When your tests are ready for integration into your organization's automation testing suite, you can add them to Jenkins or another continuous integration build system. For details, see Run tests using a CI system.

Back to top

See also: