Relevant for: GUI tests and components and API testing
When you run a test or component, UFT performs the steps it contains. If you have defined test or component parameters, UFT prompts you to enter values for them. When the run session is complete, UFT displays a report detailing the results.
For details about running business process tests, see Create and maintain business process tests and flows in UFT.
You can run UFT tests from a number of different places:
Running tests differs slightly when running GUI tests/components or API tests/components:
UFT always runs a test or component from the first step, unless you specify otherwise. You can:
|Method of Running||Description|
|Run the entire test or component from the beginning||UFT 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 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, UFT 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:
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 Maintaining 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 setp.|
|Skip certain steps if necessary||You can designate certain steps as optional, which enables UFT 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 UFT runs an iteration for each row in the Global data sheet.
Likewise, if a test action references an individual action data sheet, UFT 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.
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 GUI test with a disconnected or locked remote computer.
UFT 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, UFT 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 UFT 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.|