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

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s