Minimum permissions required for QuickTest Professional (QTP), Service Test (ST), Sprinter (SP) and/or Unified Functional Testing (UFT)

Below find the minimum required permissions on supported operating systems, for registry, folders and files, and even authentication, depending on desired tasks.

Products abreviations:

  • QuickTest Professional = QTP
  • ServiceTest = ST
  • Sprinter = SP
  • Unified Functional Testing = UFT
  • Quality Center = QC
  • Application Lifecycle Management = ALM

NOTE: All the below mentioned requirements are MANDATORY.

STANDARD USE (RUN).

Note: This is for usage/using/running only, for installation requirements, see respective session below as well as “OTHER TASKS”

Important: See below “Permissions Legend” section below for important information

  • Integrity Level: Only on Operating system where User Account Control (UAC) is ON/enabledQTP/UFT/Sprinter processes must ran with higher or equal Integrity Level than application under testing.
  • File System:

Folders / Files / Sub-folders

Permissions

Notes

Directory where product is installed (i.e.C:\Program files\HP\QuickTest Professional, C:\Program Files\HP\HP Service Test, C:\Program Files\HP\Sprinter, C:\Program Files\HP\Unified Functional Testing, etc)

Read / Write

In some situations it may be required to have read/write access permissions from higher up the folder tree. for example “C:\Program files\HP”)
TEMP directory (or TMP)

Read / Write

Start menu, select “Run”, type “%temp%”, click “Ok” or press “Enter” key.
Tests/solutions/scripts folders and its results folder.

Read / Write

For some versions/products, My Documents is default storage location
<Program Files>\Common Files\Mercury Interactive folder

Read / Write

<Program Data>\HP” folder (Start > Run > %programdata%\HP) and sub-folders/files.

Read / Write

Only Windows Vista, 7 and/or 2008.
User Profile folders (Start > Run > %userprofile%) and sub-folders/files.

Read / Write

This should grant same permissions to all sub-folders. If not, please contact local admin.
<Windows>\mercury.ini file.

Read / Write

%windir%\mercury.ini
<Windows> directory and to the system directory

Read

<Windows>\system, <Windows>\system32, <Windows>\SysWOW64
AppData folders:

  • %userprofile%\AppData\Local\HP
  • %appdata%\HP\QuickTest Professional, %appdata%\HP\Service Test, %appdata%\HP\Sprinter

Read / Write

  • Registry:

Keys / Values

Permissions

Notes

All the keys under HKEY_CURRENT_USER\Software\Mercury Interactive

Read / Write

The “Mercury Interactive” and/or QTP key are created with the first time QTP/UFT is launched
All keys under HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hewlett-Packard

Read / Write

ST / UFT only.
All the HKEY_LOCAL_MACHINE keys and to all theHKEY_CLASSES_ROOT keys

Read / Query Value

All keys under HKEY_CURRENT_USER\Software\Hewlett-Packard\Manual Runner

Read / Write

SP only
  • For working with Quality Center:

Folders / Files / Sub-folders / Keys / Values

Permissions

Notes

All permissions mentioned under “File System” and “Register” sections above

All mentioned above

Note: In some situations it may be required to have read/write access permissions from higher up the folder tree for the Temp folder.
Read and Write permissions to theQC/ALM cache directory

Read / Write

Also known as TD_80 (%temp%\TD_80)
QTP Add-in for QC or UFT Add-in for ALM installation directories

Read / Write

For some versions/products, My Documents is default storage location
First-time connecting to QC/ALM. Full permissions / UAC off This also includes first time connecting after installed new patch on server.

INSTALLATION

  • Done by full administrator permissions (even during reboot).
  • Disable the UAC (User Account Control) feature.
  • (Optional) Some environments require disabling DEP Feature:

    To disable it run this command on CMD as Administrator:  bcdedit.exe /set {current} nx AlwaysOff

OTHER TASKS

All the below mentioned tasks require pointers/bullets indicated for “INSTALLATION” section above:

  • Uninstallation of product
  • Repair or Modify (install/uninstall add-in)
  • Install Patches / Hot-Fixes
  • Setting license key
  • Changing/Switching license type (from seat to concurrent or concurrent to seat)
  • Every time QC / ALM components must be downloaded.

Permissions Legend:

  • “Read/Write”: Refers to setting/enabling “Full Control” option under “Allow” column of desired User/Group (Registry: Right click > Permissions | File/Folder: Right click > Properties > Security)
  • “Read”: Using “Read” default option set, may not be sufficient. Best to ensure all children and descendant files/folders/registry-keys/registry-values inhered setting accordingly. On registry, check with system admin about testing both options Advanced settings: “Include inheritable permissions from this object’s parent” and “Replace all child object permissions with inheritable permissions from this object”, when dealing with permissions issues.
Advertisements

2 thoughts on “Minimum permissions required for QuickTest Professional (QTP), Service Test (ST), Sprinter (SP) and/or Unified Functional Testing (UFT)

  1. kiranmayi

    Hi There. This is kiran here. I am sorry I need a solution for my sprinter immediately as I have a project deadline so I am asking you here.I have been working on sprinter in the test plan mode. During the step capture I took a few screenshots and saved the test. When I went back to HPQC application to view the test that I saved from sprinter, I see that the steps have come across but not the screenshots. Could you please guide me on the settings that need to be changed for the screenshots to come across to HPQC from Sprinter

    Reply
    1. Abdul Rahim Post author

      The screenshots captured during each run are stored in a folder inside %temp%\Sprinter folder. However, the entire %temp%\Sprinter folder is deleted every time that Sprinter is closed to avoid saving unnecessary information that could lead to memory problems. In order to extract them, the screenshots have to be copied to another location immediately after the test is run before closing Sprinter.

      If Sprinter has already been closed or the screenshots of previously executed test runs are needed, this information is also stored with the ALM test run and downloaded to %temp%\Sprinter when viewing the test run results with the Sprinter Results Viewer. Again as soon as the Results Viewer is closed, the folder is deleted. Therefore, it is also possible to extract the information even after Sprinter is closed by viewing the run details in the results viewer and copying the information from %temp%\Sprinter.

      Reply

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