This tab enables you to set options that instruct UFT which applications to open when you begin to record or run your test.
You can instruct UFT to open and record on applications from more than one environment. You can also create steps on more than one browser tab, if your browser supports tabbed browsing.
Select Record > Record and Run Settings and select the Web tab.
User interface elements are described below:
|Record and run on any open browser||
Record and run your test on any open (supported) Web browser installed locally.
You must open the Web browser after you open UFT.
To record and run tests on an application with embedded Web browser controls, select Record and run tests on any open Web browser .
You can instruct UFT to ignore ALM browsers or other browsers that are open to a specified URL or have a specific title. For details, see Web > General Pane (Options Dialog Box).
|Open the following when recording or running:||
Define whether to use a local browser, or to connect to a remote lab in Mobile Center or SRF.
Define the URL to open, and the browser to use.
|Parameterize the runtime web settings using:||
Enable to use parameters for the browser, device, and manufacturer for a given test run.
For more details, see:
UFT automatically adds columns to the Global tab of the Data pane or a test parameter, depending on the option selected.
|Remote Connection Details||
Displayed if you select Apple Safari (on remote Mac computer)
Enter the connection details for the remote Mac computer.
Default port: 8822
Values defined for the following environment variables override any values specified here during a run session:
|Do not record and run on open browsers||
Instructs UFT not to record or run tests on any browsers that are already open prior to the start of the record or run session.
Selecting this option also prevents you from viewing the properties of these browsers using the Object Spy.
|Close the browser when the test closes||
Instructs UFT to close the specific browser tab launched at the start of the test when the test closes.
For headless browsers such as Headless Chrome or Phantom JS, this closes the headless browser process launched at the start of the test.