Add tests to test suites
To run tests in the Execution submodule, include them in a test suite and specify which runner to use to run the tests. The runner you select determines where the test runs, what testing tool is used, and where the scripts are taken from.
Create a test suite with automated tests
Automated test entities represent test scripts created and stored externally. Create Automated tests by setting up a connection to the repository where your test scripts are stored. Add the tests to test suites, then schedule the test suite runs, or run them manually.
You can run all types of Automated tests in CI builds, setting up the integration as described in the Quality Management module in OpenText Core Software Delivery Platform Help Center.
UFT One or Selenium tests can be used as units in Model-Based Testing. Add the MBT tests to a test suite to run them on the OpenText cloud or in a CI build. For details, see Run MBT tests.
UFT One and Selenium tests can also run on the OpenText cloud. Add the tests to test suites that are run on a machine hosted in OpenText’s cloud environment.
To prepare a test suite with UFT One or Selenium tests to run on the cloud:
-
Configure a cloud runner to connect to your Git repository and retrieve the tests. You can work with an externally accessible Git repository, or you can set up tunneling to access a private repository.
Note: A copy of the repository is created in the OpenText cloud. If you modified the tests in the Git repository and want those changes included in your run, note the mirroring schedule defined in the cloud runner, or synchronize the repository manually.
For details, see Cloud runners for Automated tests.
-
Create a test suite and add tests using the Tests tab. For details, see Prepare and schedule test suites.
When selecting a machine for running the test, select an AMI machine with UFT One or Selenium installed.
In the test suite's Planning tab:
-
For each test, select a test runner that was configured for UFT One or Selenium, as needed.
-
If a test uses parameters, select the Data Table to use for the run.
-
Create a test suite with codeless tests
Codeless tests run on the OpenText cloud, as part of a test suite. You can schedule the test suite runs, or run them manually.
To create codeless tests and add them to a test suite:
-
Create codeless test scripts in the Design sub-module. For details, see Create a script.
-
Associate the scripts with codeless tests. For details, see Associate or unassociate your script
In a Codeless tests, the Test runner field is automatically set to Codeless Runner.
-
(Optional) Add parameters to your test, and define data sets that provide values for the parameters during a run.
-
Select the Parameters tab and click + Codeless Test Parameter. Optionally, assign a default value.
Note: If the codeless script contained parameters, they are synchronized with the test upon association.
-
The Data Sets tab contains a table where each column represents a parameter in the test, and each row represents an iteration of one set of data to be used in the test.
Enter the data you want to use in the test's parameters. Alternatively, access the More > Import Set menu command, and select a data set that you have saved in CSV format.
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.
-
-
Add the test to a test suite. For details, see To prepare a test suite.
When selecting a machine for running the test, select a machine template that contains Codeless.
In the test suite's Planning tab:
-
The Codeless Runner is selected automatically for codeless tests.
-
If a test has more than one data set, specify which data set to use.
-
Run your test suites
You can run your test suites manually, or use a scheduling mechanism to automatically run them according to your preferred schedule, such as nightly or weekly.
-
Create schedules based on your operational needs, using the Schedules tab. For details, see Create schedules.
-
Track schedule runs and execution results using the Scheduled Runs tab. For details, see Monitor test execution.
-
Use the Defects tab to manage defects related to your tests. For details, see the Issues module in theOpenText Core Software Delivery Platform Help Center.