Share this page
The following table shows the categories of output values that are supported by OpenText Functional Testing for each add-in.
Note: Only standard and bitmap output values are supported for keyword components.
Legend
- S = Supported
- NS = Not Supported
- NA = Not Applicable
Database and File Content output values
|
Database |
File Content |
|
|---|---|---|
|
.NET Web Forms |
NA |
NA |
|
.NET Windows Forms |
NA |
NA |
|
ActiveX |
NA |
NA |
|
Delphi |
NA |
NA |
|
Java |
NA |
NA |
| Mobile | NA | NA |
|
Oracle |
NA |
NA |
|
|
NA |
NA |
|
PeopleSoft |
NA |
NA |
|
PowerBuilder2 |
NA |
NA |
|
Qt |
NA |
NA |
|
SAP Web-based |
NA |
NA |
|
SAP Windows-based |
NA |
NA |
|
Siebel |
NA |
NA |
| SiebelOpenUI | NA | NA |
|
Standard Windows |
NA |
NA |
|
Stingray |
NA |
NA |
|
Terminal Emulator |
NA |
NA |
| Testing Extensibility | NA | NA |
| UI Automation | NS | NS |
|
VisualAge for Smalltalk |
NA |
NA |
|
Visual Basic |
NA |
NA |
|
Web |
NA |
NA |
|
WPF |
NA |
NA |
Standard, Table output values
|
Standard |
Table |
|
|---|---|---|
|
.NET Web Forms |
S |
S |
|
.NET Windows Forms |
S |
S |
|
ActiveX |
S |
S |
|
Delphi |
S |
S |
|
Java |
S |
NA |
| Mobile | S | NA |
|
Oracle |
S |
S |
|
|
S |
NA |
|
PeopleSoft |
S |
S |
|
PowerBuilder2 |
S |
NA |
|
Qt |
S |
S |
|
SAP Web-based |
S |
S |
|
SAP Windows-based |
S |
S |
|
Siebel |
S |
S |
| SiebelOpenUI | S | S |
|
Standard Windows |
S |
S |
|
Stingray |
S |
S |
|
Terminal Emulator |
S8 |
NA |
| Testing Extensibility | S | S |
| UI Automation | S | NS |
|
VisualAge for Smalltalk |
S |
S |
|
Visual Basic |
S |
NA |
|
Web |
S |
S |
|
WPF |
S |
S |
Text, Text Area, and XML output values
|
Text |
Text Area |
XML |
XML |
|
|---|---|---|---|---|
|
.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 |
|
|
NS |
NS |
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 |
|
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 |
|
WPF |
S |
S |
NA |
NA |
Footnotes
-
Text output values are supported only for Page, Frame, and ViewLink objects.
-
When you insert an output value step on a PowerBuilder DataWindow control, OpenText Functional Testing treats it as a table and opens the Table Output Value Properties dialog box.
-
The text area output mechanism for Java Applet objects is deactivated by default. You can activate it in the Advanced Java Options dialog box.
-
This is supported only when OpenText Functional Testing 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).
-
This is supported only when OpenText Functional Testing is configured to use the OCR (optical character recognition) mechanism.
-
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.
-
You can create text output values (tests only) only for TeScreen and TeTextScreen objects.
-
In the terminal emulator window you can add text output values (tests only) and standard output values for the status bar and the dialog boxes that open from the menu options. OpenText Functional Testing recognizes these as standard Windows objects.
