Supported controls

This is a technology preview, enabling you to experiment with AI Codeless testing.

AI Codeless Testing supports testing desktop web applications, and applications on mobile devices connected to UFT Mobile.

Supported control types

AI Codeless Testing identifies common application controls such as camera, categories, chat, check box, Facebook, favorites, radio button, share, toggle button, trash, twitter, and view. For a complete list of controls that AI Codeless Testing can identify, see the AI testing section of the UFT Help Center.

Back to top

Supported operations

The following is a list of operations that Codeless tests can perform on an identified control. In parentheses, you can find alternative names or aliases that refer to the same operations.

These are the keywords you can use for operations when writing a test step:

AI actions

  • check, uncheck (select, clear)
  • click (press, tap)

  • search (find)

  • toggle (set, switch)
  • type (enter, input)
  • Verify <object> exists
  • Verify <object> does not exist

PB (property-based) actions

  • check, uncheck (select, clear)

  • click

  • increase, decrease

  • navigate

  • set

  • select

  • toggle (set, switch)

  • Verify <object> exists

  • Verify <object> does not exist

Back to top

Reserved words

AI Codeless Testing uses the following words as part of the test step syntax:

  • the
  • for
  • into
  • that

Back to top

Test step syntax

Write your test steps in plain English, using one of the structures shown below (the words the and that are optional).

You can use single quotes or double quotes to enclose a string. The string can also contain quotes, but these quotes must be a different type than the quotes enclosing the string. See the example of Structure 3.

  • Structure 1:

    Click/press/tap the <control type>

    Example: Click the bell

  • Structure 2:

    Click/press/tap the "<text for identification>" button/text

    Example: Click the "SIGN IN" button

    Note: Text related to a class may be marked together in the user interface. This example is displayed as . Press the Backspace key twice to delete the text and class together.

  • Structure 3:

    Type "<text to type>" into "<text for identification>" input

    Example: Type "Boy's shirt" into "USER NAME" field

  • Structure 4:

    Search for "<text to find>"

    Example: Search for "Wikipedia"

  • Structure 5:

    Verify that the '<text for identification>' <control type> exists

    Example: Verify that the 'urgent' alarm exists

  • Structure 6:

    Verify that the '<text for identification>' <control type> does not exist

    Example: Verify the 'INPUT' button does not exist

  • Structure 7:

    If the '<text for identification>' <control type> exists
        <steps>
    Else
        <steps>
    

    Example:

    If the menu exists
           Click the menu
    Else
          Click the 'Close' button

    Note: The Else statement is optional.

  • Structure 8:

    If the '<text for identification>' <control type> does not exist
        <steps>
    Else
        <steps>
    

    Example: 

    If the menu does not exist
          Click the 'Close' button
    Else
          Click the menu

    Note: The Else statement is optional.

Back to top

See also: