Prepare to create a script

This topic describes the tasks you must perform before you create a codeless automation script in FT Design.

Note: This task is a part of a higher-level task. For details, see Create a script.

Before you begin

Before you begin, review the following requirements:

  • If UFT One or UFT Developer are installed, make sure they are closed before you open FT Design.

  • To test desktop web applications, make sure the extension is installed and enabled on your browser. Generally, Chrome and Edge extensions are installed with the Design Agent. See Set up the browser extension.

Back to top

Create a new script

You can create a new codeless automation script from different modules.

Submodule How to create a codeless script
Design
  1. On the Design Home page, click New script. This opens the Editor, where you can develop and edit your script.

  2. Provide a name and location for the script, and click Create script.

    A new script opens for editing.

Quality > Tests

Create a script manually from a codeless test or use the Aviator AI capabilities to generate codeless scripts based on manual tests.

Create a script manually:

  1. Create a codeless test and define test details. The Testing tool type field is automatically set to FT Design.

  2. On the Details tab of the codeless test, click Open in Design.

  3. Provide a name and location for the script, and click Create script.

A new script, already associated with the entity, is created and opened for editing.

Use Aviator to automate manual tests:

  1. Select one or more manual tests in the Tests tab.

  2. Click the Generate Codeless Test button .

A codeless test and associated script are generated for each manual test. For details on working with generated scripts, see Automate manual tests with Aviator.

Model-Based Testing > Units
  1. Create a unit.

  2. Set the unit's Testing tool type to FT Design.

  3. On the Details tab of the unit, click Open in Design.

  4. Provide a name and location for the script, and click Create script.

    A new script, already associated with the unit, is created and opened for editing.

Naming conventions

A script's location is a path (folders and subfolders) within the current workspace. The folders and subfolders must exist before you save a script to that location.

Script and folder names can include English letters, numbers, spaces, dots ('.'), dashes ('-'), and underscores ('_').

The names cannot start with a space or dot ('.').

Back to top

Configure your applications

When you develop a script, you need to add applications on which to run the script.

You can add up to 3 applications. Build your script using one application, and then run the script on all the applications in a single run session, one after the other.

To add desktop web applications:

  1. Make sure that your browsers are set up for web testing. For details, see Before you begin.
  2. Open a codeless automation script.

  3. Click the Script applications icon.

  4. In the Script applications pane that opens, click + Add new application.

  5. Select a browser and enter the application URL.

    Click the icon to use an input parameter for the browser or URL. For details on using parameters, see Pass a value to the script

    Note: When you run the script, any parameters you use in the application definition must have a value. This can be a default value, or a value provided by a data set.

    Click Apply.

  6. Repeat the above steps to add up to 3 applications.
  7. To edit or delete an application, click the ellipsis button on the application card and select Edit or Delete .

Back to top

Launch your application

Launch one of the applications that you want to test.

To launch your application:

You can launch your application either in the Script applications pane or in the AI Inspect window.

In the Script applications pane, click the ellipsis button on an application card and select Launch .

The application opens in a web browser. Now you can click the Inspect application button to inspect your application and create steps. For details, see Create steps by inspecting your application.

Back to top

Next steps: