List of the default and available properties for various objects

Refer to the Object Identification utility and the Object Model Reference

You can find a list of the available Test Object properties for objects in the Object Model Reference.

QuickTest Professional 9.x
1. Go to Help -> QuickTest Professional Help.
2. Go to Object Model Reference -> -> -> Properties. 3. Select the Identification Properties link.

Example:
Object Model Reference -> Java -> JavaButton Object -> Properties -> JavaButton Identification Properties

QuickTest Professional 8.0
1. Go to Help -> QuickTest Professional Help.
2. Go to Object Model Reference -> -> Test Object Properties. 3. Select the link for the desired Test Object.

Example:
Object Model Reference -> Visual Basic -> Visual Basic Test Object Properties -> VbList Test Object Properties

QuickTest Professional 6.5
1. Go to Help -> QuickTest Professional Help.
2. Go to Object Model Reference -> -> 3. Select the Test Object Properties link.

Example:
Object Model Reference -> Visual Basic -> VbList Object -> VbList Test Object Properties

For the default properties used to identify objects, refer to the Object Identification tool. 1. Go to Tools -> Object Identification.
2. In the “Environment” drop-down, select the appropriate option.

Example:
Standard Windows for Dialog or Window objects.
Web for WebEdit or Browser objects.

3. Select the desired Test Object Class from the left column. The tables to the right will be populated with the values.

The values listed in the Mandatory table are always used (if they have a value) to identify objects of the selected class. The assistive properties are used if the mandatory properties do not uniquely identify the object. You can use the Add/Remove options to customize the mandatory and assistive property lists.

To reset to the defaults, click . This will return the settings for all objects back to the default values, not just the class that is highlighted.

Advertisements

Text recognition operations on Windows Vista, 7 or 2008 are not always reliable

On Windows Vista, 7 or 2008 operating system (32bits or 64bits), QuickTest Professional (QTP) 9.X or higher version’s text recognition features (such as text checkpoints and output values, GetVisibleText and GetTextLocation test object methods, and TextUtil.GetText and TextUtil.GetTextLocation reserved object methods) are limited and are not always reliable.

Note: By design, text recognition on Windows Vista, Windows 7 and Windows 2008 can only use/work-with OCR setting instead of Windows API, which may result on capture text being less accurate or reliable as on older operating systems. Below are alternatives/suggestions to try improving the OCR results

* Minimize searching area. Setup the seach of text to smaller range/area, for example GetVisibleText method, includes parameters “left”, “top”, “right” and “bottom” to define the search area.
Note: If the Left, Top, Right, and Bottom arguments are not specified, the method returns all of the text within the visible part of the specified object. * Applying the Classic Windows theme:
1. Right click on the your desktop and select “Personalize.” 2. Click on the Theme link to bring up the Theme Settings dialog. 3. Under Theme, select “Windows Classic.”
* The larger the text, the better the text recognition. Either setup the operating system to display character size as bigger, or make character size bigger in the application. Check the operating system’s settings to increase font or DPI size, or the application’s developers for text only on the application.
* Ensure QuickTest Professional is using the OCR only mode for text recognition.
* For QTP 10 or higher, try setting up “Single text block mode” in the General > Text Recognition pane of the Options dialog box.

Difference between the Test Batch Runner and Automation Object Model

The Test Batch Runner is a dedicated utility:
* Found under Start > Programs > QuickTest Professional / Unified Functional Testing > Tools > Test Batch Runner. * Allows to run several scripts together (in a “batch”)

The Automation Object Model (AOM) is the QuickTest Professional’s API (Application Programming Interface), a feature (not an utility).

Determine if correct files and registries are being used by tool

When utilizing QuickTest Professional (QTP), Unified Functional Testing (UFT) or other tools, changes done on some files and/or registries used by such tools are not taking effect or reflecting on expected file paths.

Some examples among many:

* Changes done on C:\Windows\Mercury.ini are not affected QTP/UFT

* Log configuration done on \bin\log.config.xml, is not reflecting on logs outputs from %appdata%\Hewlett-Packard\UFT\Logs\

* Modifications to registry paths
Ensure file/registry paths attempting to modify, are actually being used by mentioned tools.

There are Windows features or third party applications used on servers, to reallocate/redirect user’s specific folders/files to a profile-dedicated location, which may interfere how HP tools work.

How to determine if an HP tool is using or outputting data to desired location?

HP recommends using a monitoring tool, for example Microsoft Process Monitor tool, to spy on the tool’s executable (UFT.exe, QTPro.exe, etc) while it accesses all its related files/registries.

Some examples

There are scenarios where restricted (and/or virtualized) environments implement use of Microsoft’s Virtual Store, imposed by User Account Control (UAC), redirecting applications to use a virtualized version of some files/folders/registries, therefore respective users manipulate copies of such.

Note: Some HP software features, read direct/absolute paths within Windows, not relative paths. Some examples:

Mercury.ini file:

* Original path: C:\Windows\

* Virtualized path: C:\Users\\AppData\Local\VirtualStore\Windows\mercury.ini

QTPEssentials registry key:

* Original path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mercury Interactive\QuickTest Professional\CurrentVersion

* Virtualized path: HKCU\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Mercury Interactive\QuickTest Professional\CurrentVersion

Note: there are 3rd party software which implement similar behavior, such as AppSense

Enable Unified Functional Testing (UFT) logs

Previously, QuickTest Professional used tool \bin\ClientLogs.exe utility, setting up its section called “QTP”, however for UFT, this option does not capture any logs.

Implement the below solution to capture UFT logs considering the above

Instructions to collect desired logs.

IMPORTANT: Review entire below summary before implementing steps.

1. Close UFT.exe, AQTRmtAgent.exe and QTAutomationAgent.exe

2. Locate tool’s “Logs” directory/folder (see A section below)

3. Configure all necessary config.xml files (see B section below)

4. Clear (or delete contents of) “Logs” directory/folder.

5. Reproduce situation. If reproduction requires multiple repetitions/iterations, repeat steps 4 – 5.

Note: Enabling logs as suggested may generate larger logs files, so minimizing the tasks done on UFT to reproduce, and clearing the logs before each attempt of reproduction, may help collecting more accurate information from such logs.

6. (If possible) Collect date and time when issue. Note: this helps narrowing down search within logs.

7. Compress logs to ZIP
A. Logs location/path/directory

The UFT log files generated from below steps should get created by default under the following path:

%APPDATA%\Hewlett-Packard\UFT\Logs
or
C:\Users\\AppData\Roaming\Hewlett-Packard\UFT\Logs

To navigate to above, go to “Start” > “Run” and type above path.

Note: if, and only IF, above path is not found, then:

1. Open desired log configuration file (*.xml)

2. Search below tag/structure:

3. Confirm “file value” is pointing to desired path.
Note: Above is pointing to default mentioned before/above: %APPDATA%\Hewlett-Packard\UFT\Logs

4. (Optional) If desired, change path to another location and save file, for example:

B. Configure config.xml files

1. Create backup of \bin\log.config.xml. Note: this is to “disable” expanded logs by replacing modified files with backup

2. Open on a text editor \bin\log.config.xml

3. If the test execution is longer than 30 min, increase the value of maximumFileSize to 50MB:

4. Change the “level value” under “root” tag to DEBUG (instead of ERROR):

5. Make sure all appender-ref element values are set to “RollingFileAppender”:

6. If involving API scripts, add logger/tag named “HP.ST” as below:

7. Save changes on log.config.xml

8. Repeat steps 1 to 5 for below files \bin\log.config.AutomationAgent.xml, THEN save changes.

9. For \bin\log.config.RemoteAgent.xml, repeat steps 1 to 5, THEN set “level value” to DEBUG, under “LogCatRmtAgent” logger:

10. For \bin\qeee.log.config.xml, repeat steps 1 to 4, THEN:

1. Make sure all appender-ref element values are set to “QEEE_RollingFileAppender”:

2. Set “level value” to DEBUG, under “HP.QTP.QEEE” logger:

Objects are not recognized in the AUT while working with a business component in UFT

UFT 11.5X / 12.0X is unable to identify objects from the application under test for a business component test.

This happens even if the application area has been created with the required add-ins and they’re also currently loaded from the testing tool.

The cause of this is because the specific technology/add-in support is not being injected to the target application process.

To fix this issue, as specified in UFT Help documentation at:

UFT User Guide > UFT Configuration > Settings for GUI Tests, GUI Business Components, and Application Areas > Reference > Applications Pane (Business Component Settings Dialog Box / Application Area – Additional Settings Pane)

“Lists the details of the Windows-based applications on which to record and run components associated with this application area. For details on the details displayed, see Select Application Dialog Box.

If you do not want to record or run on Windows-based applications, leave the application list blank. (This is the default setting.)”

It’s a requirement for applications for scenarios where a process name can be identified for the application under test (ActiveX, Net, WPF, PowerBuilder, etc…) to include it in the list of applications to record and run.