Defining test environments
After you create tests and test sets in HP Quality Center that are based on HCL OneTest™ API test artifacts, you define the environments for test execution.
About this task
In HP Quality Center, open the Test Lab module.
Procedure
- Open a test set that contains your HCL OneTest™ API tests.
- Open the Test Instance Details window for a selected test (double-click the test in the Execution Grid, or right-click and select Test Instance Details).
- Click Execution Settings, and then click the Automated tab.
-
Select a test environment from the list.
You can select any of the environments in the project that contain
the linked HCL OneTest™ API test.
To update the list of available environments, click Refresh.
Note: You must select a test environment: otherwise, tests will not run successfully.
-
Click the Set as Default button
to set the currently selected environment as the default environment
for any tests that are linked to the same HCL OneTest™ API project
as the test that is being edited.
You are prompted to confirm your selection.
Using this option, if no environment is set explicitly for a test, it uses the default environment for the project to which it is linked.
Note: Default environments are a user setting within Quality Center, so they are set only for the user who sets them. -
Select the execution method for the test. You can also
make this as the default test execution method.
- To run all the tests in the test set continually, select Running
Tester instance. Use this option to run test sets that
contain multiple tests and improve the speed of the test run. If
HCL OneTest™ API is not running, it starts and loads the correct project to
run the test and to continue running.
- To confirm each time the project is loaded during the test execution, select the Prompt before loading RIT projects option. Clear this option to automatically load the projects while running the tests on a remote or unattended hosts.
- To refresh the project before each test set is executed, select
the Refresh RIT project option. Note: Select this option to ensure that the project is not out of date and you get the correct results. There might be a performance degradation because the project is refreshed even when it is not needed.
- To indicate the Quality Center to wait for HCL OneTest™ API to execute a test before timing out, specify the duration in the Timeout field.
- To run tests individually (so that the HCL OneTest™ API project opens and closes for each test run), select Command line (Legacy). This method is convenient if you are running test sets that only contain a few tests or if the test set contains tests from multiple HCL OneTest™ API projects.
- To run all the tests in the test set continually, select Running
Tester instance. Use this option to run test sets that
contain multiple tests and improve the speed of the test run. If
HCL OneTest™ API is not running, it starts and loads the correct project to
run the test and to continue running.
-
Define the level of messages to display in the log file.
The name of the log file is GHRunAgentOutput_n (where n is
a number). In Log level, select one of the
following options:
- Off
- Severe
- Warning
- Info
- Debug
- Click OK, and then click Close to close the Test Instance Details window.