AI-based testing: Supported control types
Mobile, web, and windows-based SAP GUI tests
This topic lists the control types that UFT One can recognize using Artificial Intelligence (AI).
Supported control types
Below is the list of control types that UFT One can identify 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 | Comments |
---|---|---|---|
bag | shopping_bag |
![]() |
|
bell | alarm, notification |
![]() |
|
button | |||
calendar (tech preview) |
![]() |
||
camera |
![]() |
||
categories |
![]() |
||
chat |
![]() |
||
chart |
graph |
![]() ![]() |
Supported only on:
|
check_box | checkbox, togglable | ||
check_mark |
tick |
![]() ![]() |
|
clock |
time |
![]() |
Supported only on:
|
close | clear |
![]() |
|
combo_box |
combobox, field |
![]() |
|
contact card |
![]() ![]() ![]() |
|
|
copy |
![]() ![]() |
|
|
display |
Glasses |
![]() |
|
document |
File |
![]() ![]() ![]() |
Supported only on UFT One 2022 and later |
dot_menu | menu |
![]() |
|
down_triangle | collapse, down |
![]() |
|
enter |
![]() ![]() ![]() |
|
|
eq_settings | settings |
![]() |
|
exit |
![]() ![]() ![]() |
UFT One versions 2021 R1 and earlier: Supported only on mobile applications |
|
![]() |
|||
favorites | rating, star |
![]() ![]() |
|
filter |
![]() |
Supported only on mobile applications |
|
find |
![]() ![]() ![]() |
|
|
folder |
![]() ![]() |
|
|
forward |
![]() ![]() |
|
|
gear_settings | settings |
![]() |
|
hamburger_menu | menu |
![]() ![]() |
|
help |
![]() |
||
home |
![]() |
||
info |
![]() |
||
input | field, edit, editfield | ||
|
![]() ![]() ![]() |
Not supported on mobile applications | |
left_arrow | left |
![]() |
|
left_triangle | left, back, previous |
![]() |
|
|
![]() ![]() |
Not supported on mobile applications |
|
location |
![]() |
||
lock |
![]() |
Supported only on mobile applications |
|
![]() |
|||
minus |
subtract, zoom_out |
![]() |
|
pencil | edit |
![]() |
|
people |
group, team |
![]() |
Supported only on:
|
pin |
![]() ![]() ![]() |
|
|
phone | call |
![]() |
|
plus |
add zoom_in |
![]() |
|
power |
![]() |
||
profile | person, user |
![]() |
|
radio_button | radiobutton, togglable |
![]() |
|
refresh |
reload, replace, sync |
![]() ![]() ![]() |
Supported only on:
|
right_arrow | right |
![]() |
|
right_triangle | right, next, forward, play |
![]() |
|
rss_feed |
rss |
![]() ![]() |
Not supported on mobile applications |
save |
![]() ![]() |
|
|
schema |
Org Chart |
![]() ![]() ![]() |
|
search |
![]() |
||
share |
![]() |
||
shopping_cart | cart |
![]() |
|
sort |
![]() ![]() |
Supported only on mobile applications |
|
table (tech preview) |
Not supported on mobile applications | ||
text | |||
text_box includes multi-line text boxes |
textbox, field |
![]() ![]() |
|
toggle_button | toggle, switch, togglable |
![]() |
|
tool_settings | settings |
![]() |
|
trash | delete |
![]() |
|
![]() |
|||
up_arrow |
up |
![]() |
Not supported on mobile applications |
up_down |
![]() |
Not supported on mobile applications | |
upload |
![]() |
Supported only on mobile applications |
|
up_triangle | up |
![]() |
|
view |
![]() |
||
window |
![]() ![]() ![]() |
|
|
Youtube |
![]() |
Not supported on mobile applications |
Note:
-
An underscore can be replaced with a space.
-
Use the text class only in AI Codeless Testing tests. In UFT One, identify text objects using the AIUtil.FindText or AIUtil.FindTextBlock methods.
-
Class names are case insensitive.
UFT One version 2021 R1 only: Class names are case sensitive.
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 (tech preview)
In UFT One, 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, UFT One displays the corresponding hierarchy of the control.
Note:
-
Only table-like calendar controls are supported.
-
Table cell objects are identified using ABBYY OCR. UFT One versions 2021 R1 and later: To identify TableCell objects, you must have the ABBYY OCR Engine feature installed in UFT One.
For more details, see the AICalendar Object and AITable Object object reference in UFT One Object Model Reference for GUI Testing.
Control types that can be identified by text
Controls of the following types can be more specifically identified by their text:
- button
- check box
- combo box
- input
- radio button
- text box
- toggle button
Feedback regarding supported control types
When using AI to inspect your application for objects, you can send feedback directly to Micro Focus. Using this tool, you can do the following:
-
Send anonymous feedback to the Micro Focus server.
Comment on how well AI 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 AI-based testing Feedback Tool.
See also: