Troubleshooting FT Design

This topic describes some unexpected scenarios that may occur with FT Design, and explains what to do if they occur.

Runtime errors

If you try to run a script and it fails immediately, open the %localappdata%\VEFTDesign\CodelessAgent\Logs\codeless.executer.log file for more details.

The table below explains what to check for different errors that might occur when running a script:

Error message What to do

No item detected for class <class>.

  • Make sure the application was launched correctly.
  • Make sure the application is in the correct state.
  • Make sure the object is visible on the screen.
Detection not unique for class <class>.
  • Make sure the application was launched correctly.
  • Make sure the application is in the correct state.
  • Make sure there is only one object of the required class.

Back to top

Verification misled by misspelling indication

Running a Verify step on text may fail if the text is displayed with a misspelling indication, such as a wavy line under the text.

Use one of the following workarounds:

  • Deactivate spell checking in your browser or application.

  • Before the Verify step, add a step that clicks another location, to remove the focus from the text and clear misspelling indication.

Example: The following example adds a step before the Verify step to move the focus away.

Copy code 
Click the profile
Type "naame" into "Username" input
Click the "Username" text 
Verify that the value of "Username" input is "naame"

Back to top

Handle slow-loading sites

At the beginning of a test run, the run waits for a few seconds to allow time for the web page to load.

In some cases, you might find that your application needs more time to load before the script starts running.

In other cases, a step's object might be slow to display on the page after the previous step ran.

To make sure steps are performed only when your application is ready for them, you can add Verify <object> exists or Wait (seconds) steps.

For details, see Synchronize your script.

Back to top

Connecting to the AI Object-Detection Cloud Service

If an error occurs when connecting to the AI Object-Detection Cloud Service, try to resolve the issue by configuring the proxy settings for the agent. See Connect to the AI Object-Detection Cloud Service.

Back to top

Logs

If any error occurs, for which you need additional information, check the %localappdata%\VEFTDesign\CodelessAgent\Logs folder for more details about the error.

Back to top

Provide information for a support ticket

If you open a support ticket about one of the following situations, providing additional information can be helpful: 

  • Inspection fails to identify your objects.

  • When you run tests or scripts, steps with specific objects fail.

To assist with handling your request, attach an image of your application, as the inspection sees it. To obtain the image, inspect your application or mockup image, click the AI Inspect window's Help menu and select Download image.

For more details on inspection, see Create steps by inspecting your application or Create steps by inspecting mockups.

Back to top

General error

If FT Design always fails to connect to the AI Object-Detection Service, your proxy may be replacing the service's communication certificate.

  • When inspecting an application, a general error occurs.

  • When running a script, steps fail, with an error in the run results indicating failure to connect to the AI service.

Solution: Contact support to help you obtain your AI Object-Detection Service's certificate and install it locally.

Caution: Make sure your company's security policy permits installing certificates.

Back to top