AI-based testing: Supported control types

This topic lists the control types that can be recognized using Artificial Intelligence (AI).

Relevant products and test types

This topic is relevant for the following products and test types:

Product Test types
OpenText Functional Testing Web, mobile, and windows-based SAP GUI tests.
OpenText Functional Testing for Developers Web and mobile tests.
OpenText Core Software Delivery Platform Functional Testing Design  Codeless scripts.

Back to top

Supported control types

Below is the list of control types that can be identified using AI. The aliases defined for each class are alternative names that refer to the same controls. They are the keywords you can use for a control's type or class, when describing a control for a test step.

Class Aliases Examples Supported on Mobile?
bag shopping_bag Yes
bell alarm, notification Yes
button (no alias) Yes
calendar (tech preview) (no alias) Yes
camera (no alias) Yes
categories (no alias) Yes
chat (no alias) Yes

chart

 graph

Only on Mobile
check_box checkbox, togglable Yes

check_mark

 tick Yes

clock

 time

Only on Mobile
close clear Yes

combo_box

 combobox, field Yes

contact card

 (no alias)

No

copy

 (no alias)

No

display

 Glasses

No

document

 File

Yes
dot_menu menu Yes
down_triangle collapse, down Yes

enter

 (no alias)

No
eq_settings settings Yes

exit

 (no alias)

Yes
facebook (no alias) Yes
favorites rating, star Yes

filter

 (no alias)

Only on Mobile

find

 (no alias)

No

folder

 (no alias)

No

forward_to

 forward

No
gear_settings settings Yes
hamburger_menu menu Yes
help (no alias) Yes
home (no alias) Yes
info (no alias) Yes
input field, edit, editfield Yes

instagram

 (no alias) No
left_arrow left Yes
left_triangle left, back, previous Yes

linkedin

 (no alias)

No
location (no alias) Yes

lock

 (no alias)

Only on Mobile
mail (no alias) Yes

minus

 subtract, zoom_out Yes
pencil edit Yes

people

 group, team

Only on Mobile

pin

 (no alias)

No
phone call Yes
plus

add

zoom_in

 Yes
power (no alias) Yes
printer print

Only on Mobile
profile person, user Yes
radio_button radiobutton, togglable Yes

refresh

 reload, replace, sync

Only on Mobile
right_arrow right Yes
right_triangle right, next, forward, play Yes

rss_feed

 rss

No

save

 (no alias)

No

schema

 Org Chart

No
search (no alias) Yes
share (no alias) Yes
shopping_cart cart Yes

sort

 (no alias)

Only on Mobile

table (tech preview)

 (no alias) No
text (no alias)

Yes

text_box

includes multi-line text boxes

 textbox, field Yes
toggle_button toggle, switch, togglable Yes
tool_settings settings Yes
trash delete Yes
twitter (no alias) Yes

up_arrow

 up No

up_down

 (no alias) No

upload

 (no alias)

Only on Mobile
up_triangle up Yes
view (no alias) Yes

window

 (no alias)

No

Youtube

 (no alias) No

Note:  

  • In OpenText Functional Testing and OpenText Functional Testing for Developers, an underscore in a class name can be replaced with a space.

  • Class names are case insensitive.

  • Combo boxes are not supported in codeless scripts.

  • text class:

    • Use to describe text strings only.

    • Use only in codeless scripts.

    • In OpenText Functional Testing, identify text objects using the AIUtil.FindText or AIUtil.FindTextBlock methods.

You can use general names to include multiple control types:

Generic name Used for Included controls
down down triangles down_triangle
field areas that accept text input, text_box, combo_box
left left pointers left_arrow, left_triangle
menu buttons that open a menu dot_menu, hamburger_menu
right right pointers right_arrow, right_triangle
toggleable, togglable Controls with changing states check_box, toggle_button, radio_button
up up pointers up_triangle, up_arrow

Calendar and table containers (OpenText Functional Testing, tech preview)

In OpenText Functional Testing, as a tech preview, calendar and table controls can be used as container objects. Creating an object hierarchy helps create more resilient AI-based tests and increase test coverage.

When using AI object identification, if you choose to use calendar and table controls as containers, you can easily interact with the containers and the elements inside them. When you inspect or record a container control, OpenText Functional Testing displays the corresponding hierarchy of the control.

Note:  

  • Only table-like calendar controls are supported.

  • Table cell objects are identified using ABBYY OCR. To use AITableCell objects, you must have the ABBYY OCR Engine feature installed in OpenText Functional Testing.

For more details, see the AICalendar Object and AITable Object object reference in Object Model Reference for GUI Testing.

Back to top

Control types that can be identified by text

Controls of the following types can be more specifically identified by their text: 

  • button
  • checkbox
  • combo box
  • input
  • radio button
  • text box
  • toggle button

Back to top

Supporting Select operations on combo boxes

This section describes when OpenText Functional Testing supports running the combo box Select operation.

Mobile testing:

The Select operation is supported on a combo box identified by AI only if OpenText Functional Testing can also identify the combo box as a MobileDropDown.

Non-mobile testing:

If possible, the combo box is identified as a WebList, as the Select operation is most efficient when using the object's native commands.

Otherwise, AI capabilities are used to support the Select operation. In this case, the operation is affected by the AIRunSettings.ComboBoxSelect settings. These runtime settings specify how far and in which direction to scroll the combo box's list in search of the specified value.

The AI-based Select operation is supported on combo boxes with a simple drop-down list that opens by clicking the box.

Select is not supported on combo boxes that do not meet these conditions, for example: 

  • Combo boxes that open when hovered over

  • Combo boxes that open only by clicking the down arrow

  • Combo boxes with complex drop-down lists, such as lists with multiple columns, or list items displayed horizontally.

Back to top

Feedback regarding supported control types

This section is relevant for OpenText Functional Testing and OpenText Functional Testing for Developers.

When using AI to inspect your application for objects, you can send feedback directly to OpenText. Using this tool, you can do the following:

  • Send anonymous feedback to the OpenText server.

    Comment on how well AI Object Inspection identified the objects in your application and help improve the identification in the future.

  • Save your feedback locally and attach it to a support ticket.

    If you need help with object identification in your application, open a support ticket and provide the details using the feedback tool.

See Send AI Object Identification feedback.

Back to top

See also: