Supported Output Values

Relevant for: GUI tests and components

The following table shows the categories of output values that are supported by UFT for each add-in.

  • S = Supported

  • NS = Not Supported

  • NA = Not Applicable

  • Note: Only standard and bitmap output values are supported for keyword components.

Accessibility, Bitmap, Database, and File Content checkpoints

 

Accessibility

Bitmap

Database

File Content

.NET Web Forms

NA

NA

NA

NA

.NET Windows Forms

NA

NA

NA

NA

ActiveX

NS

NA

NA

NA

Delphi

NS

NA

NA

NA

Java

NA

NA

NA

NA

Mobile NA NA NA NA

Oracle

NA

NA

NA

NA

PeopleSoft

NA

NA

NA

NA

PowerBuilder2

NA

NA

NA

NA

Qt

NA

NA

NA

NA

SAP Web-based

NA

NA

NA

NA

SAP Windows-based

NA

NA

NA

NA

Siebel

NA

NA

NA

NA

SiebelOpenUI NA NA NA NA

Silverlight

NA

NA

NA

NA

Standard Windows

NA

NA

NA

NA

Stingray

NA

NA

NA

NA

Terminal Emulator

NA

NA

NA

NA

Testing Extensibility NA NA NA NA
UI Automation NS S NS NS

VisualAge for Smalltalk

NA

NA

NA

NA

Visual Basic

NA

NA

NA

NA

Web

NA

NA

NA

NA

Windows Runtime NA NA NA NA

WPF

NA

NA

NA

NA

Back to top

Image, Page, Standard, and Table checkpoints

 

Image

Page

Standard

Table

.NET Web Forms

NA

S

S

S

.NET Windows Forms

NA

NA

S

S

ActiveX

NA

NA

S

S

Delphi

NA

NA

S

S

Java

NA

NA

S

NA

Mobile NA NA S NA

Oracle

NA

NA

S

S

PeopleSoft

NA

S

S

S

PowerBuilder2

NA

NA

S

NA

Qt

NA

NA

S

S

SAP Web-based

NA

S

S

S

SAP Windows-based

NA

S4

S

S

Siebel

NA

S

S

S

SiebelOpenUI NA S S S

Silverlight

NA

NA

S

S

Standard Windows

NA

NA

S

S

Stingray

NA

NA

S

S

Terminal Emulator

NA

NA

S8

NA

Testing Extensibility NA NA S S
UI Automation NS NS S NS

VisualAge for Smalltalk

NA

NA

S

S

Visual Basic

NA

NA

S

NA

Web

NA

S

S

S

Windows Runtime NA NA S S

WPF

NA

NA

S

S

Back to top

Text, Text Area, and XML checkpoints

 

Text

Text Area

XML
(Application)

XML
(Resource)

.NET Web Forms

S5

S5

NA

NA

.NET Windows Forms

S5

S5

NA

NA

ActiveX

S

S

NA

NA

Delphi

S

S

NA

NA

Java

S

S3

NA

NA

Mobile S NS NA NA

Oracle

NA

NA

NA

NA

PeopleSoft

S1

NS

S

S

PowerBuilder2

S

S

NA

NA

Qt

S

S

NA

NA

SAP Web-based

S

NS

S

S

SAP Windows-based

S4

NS

S4

S

Siebel

S

NS

S

S

SiebelOpenUI S1 S S6 NA

Silverlight

S

S

NA

NA

Standard Windows

S

S

NA

NA

Stingray

S

S

NA

NA

Terminal Emulator

S7

NA

NA

NA

Testing Extensibility S1 S NA NA
UI Automation S S NS NS

VisualAge for Smalltalk

S

S

NA

NA

Visual Basic

S

S

NA

NA

Web

S1

NS

S6

NA

Windows Runtime S S NA NA

WPF

S

S

NA

NA

Back to top

Footnotes

1 Text output values are supported only for Page, Frame, and ViewLink objects.

2 When you insert an output value step on a PowerBuilder DataWindow control, UFT treats it as a table and opens the Table Output Value Properties dialog box.

3 The text area output mechanism for Java Applet objects is disabled by default. You can enable it in the Advanced Java Options dialog box.

4 This is supported only when UFT records HTML elements using the Web infrastructure, but not when it records using the SAPGui Scripting Interface (as selected in the SAP pane of the Options dialog box).

5 This is supported only when UFT is configured to use the OCR (optical character recognition) mechanism.

6 XML output values are not supported on Internet Explorer 9 or later running in standard mode, on Google Chrome, or on Mozilla Firefox, because the WebXML test object is not supported for these browsers.

7 You can create text output values (tests only) only for TeScreen and TeTextScreen objects.

8 In the terminal emulator window you can add text checkpoints or output values (tests only) and standard checkpoints and output values for the status bar and the dialog boxes that open from the menu options. UFT recognizes these as standard Windows objects.

Back to top