Known issues in FT Design

This topic describes the known issues when working with FT Design.

Step syntax

When writing a step in a codeless script, do not include apostrophes, single quotes, or double quotes in a string.

Example: This step is not valid: Type 'Boy's shirt' into 'Description' field

Text recognition

When the cursor is displayed in or near a text string in the tested application, the text may not be identified properly. Consider adding steps to your test that place the cursor elsewhere before trying to identify or verify text.

Soft menu buttons

When creating steps in a codeless script, make sure not to click soft menu buttons. These buttons are not supported when running the script.

Spy

The following issues exist when you use the built-in Spy to add steps to your codeless script.

Select operation not supported for Web tables

For a Web table, only the Click operation is supported when you spy on an object in the table. If you change the operation of a step added by using the Spy to Select, the step run fails.

Run scripts

When running codeless scripts in FT Design, you may encounter the following issues:

Browsers displaying occasional pop ups or bars

Scripts fail to run in the following situations:

Running on a Firefox browser if a pop-up window is displayed at the bottom of the browser.
Running on a Chrome browser if a download bar is displayed at the bottom of the browser.

Calendar and table objects

Calendar and table objects are only supported in Property Based steps.

Scaling

Steps fail to run on computers that use a display scaling level other than 100%.

Associating scripts

If a script's path is longer than 512 characters, it cannot be associated with a codeless test or unit.

Multiple monitors

When working with multiple monitors, make sure that FT Design and the application you are testing are visible on the primary monitor.

Managing changes from multiple sessions

If the same script is modified at the same time in different sessions, the last save overwrites any previous changes. This can happen when different users modify the same script, or even if you opened the same script in multiple browser tabs.

Similarly, you may encounter the following issues:

If changes are made to parameters in a codeless test and in its associated script, the last changes saved overwrite any previous ones that were not yet synchronized.

Before editing a previously opened test, script, or unit, you may want to make sure you include any changes saved in another session. To do this, reopen, refresh, or reload the open script, test, or unit.
A script or folder might be renamed, moved, or deleted in another session, but you will not be aware of this until you refresh the list of scripts in the script tree pane or the Home page.

Before renaming, moving, or deleting a script or folder, you may want to make sure you include any changes made in another session. To do this, refresh the script tree pane using the refresh button, or refresh the FT Design browser page.

Navigating within FT Design

To open the script editor, displaying the script steps, click a script name in the Script tree pane or on the FT Design Home page.

To return from the script editor to the Home page, use the Home button.

Using the browser's Back and Forward buttons to switch between the editor and the Home page is not supported.

Selecting from an auto-complete list

To select from an auto-complete list in your tested application, you might have a step that sets a string into an edit box, and then a step that clicks the relevant item in the list that pops up.

For example, when selecting a city for a flight, you might write the following script:

Enter "New York" in the "From" text_box
Wait 5 seconds
Click the "NYC - New York, NY" text

In some cases, the wrong entry in the auto-complete pop-up list is selected.