Can Sprinter and QuickTest Professional(QTP) be run simultaneously

This is a documented limitation of Sprinter. Sprinter and QuickTest Professional cannot be run simultaneously on the same computer.

A Note Regarding Installation – You will be able to install Sprinter and QuickTest professional on the same computer only when the versions match. For example you can install Sprinter 11.0 and QuickTest Professional 11.0 on the same computer. However, you cannot install Sprinter 11.0 and QuickTest Professional 10.0 on the same computer.

QTP 11 crashes on startup after removing Sprinter 11.5

After removing Sprinter 11.5, QTP 11 doesn’t start anymore. It crashes with a Visual C++ runtime error.

1. Delete following Sprinter folders and registry keys which may have remained after its reinstallation:

32-bit Windows:

• C:\Program Files\HP\Sprinter

• %appdata%\HP\Sprinter

• HKEY_CURRENT_USER\Software\Hewlett-Packard\Manual Runner

• HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\Manual Runner

64-bit Windows:

• C:\Program Files (x86)\HP\Sprinter

• %appdata%\HP\Sprinter

• HKEY_CURRENT_USER\Software\Hewlett-Packard\Manual Runner

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hewlett-Packard\Manual Runner

2. Uninstall QTP

3. Uninstall from Windows Control Panel all versions of Visual Studio C++ Runtime Libraries

4. Reinstall QTP and its prerequisites

Download and install Debugging Tools for windows

Download Instructions:

· Download sdksetup.exe from (Install Debugging Tools for Windows as a Standalone Component (from Windows SDK) )

· Run "sdksetup.exe", press “Continue”

· Press next (default location on Win 7 would be "C:\Users\<User>\Downloads\Windows Kits\8.0\StandaloneSDK"

· Select “Debugging Tools for windows” option and press download

· Navigate to directory specified in point "#3" and run "sdksetup.exe"

SDK setup:

· Run "sdksetup.exe"

· Specify location (default: C:\Program Files (x86)\Windows Kits\8.0\)

· Follow instructions (mainly press next…) and you can ignore warnings about .NET 4/4.5 missing frameworks . If you have such errors it means these frameworks are not installed on your computer , that indicates your application is not using it

Error messages displayed during data injection

When trying to inject data (HP Sprinter) in a specific application where two fields of the user interface have the same label, some error messages appear:

"More than one field label in your application matches a field name in your data set"

"Two Fields with the same label causes Problems within Data Injection (DaIn)"

For example, this can be reproduced when injecting the passenger data to book a flight in the "Mercury Tours" demo application as both the "Passengers" and "Credit Card" sections have a "First Name:" field.

HP Sprinter uses the field label to inject the data. Therefore, if two fields have exactly the same label, it is necessary to add information to enable Sprinter to uniquely recognise each of them.

The recommendation in this situation is not to use data injection against these fields. However, it is possible to work around the problem using the below

· Enable Sprinter Power Mode

· Create a data set.

o Review "Guidelines for Creating Data Injection Data Sets" (HP Sprinter User Guide)

· Associate the data set with your application.

· (Optional) Define which fields you want to inject, and what order (optional).

· Ensure only one instance of related application is opened.

· Run a test.

· Once desired fields are displayed/visible, access/go to the "Data Injection" tab/panel

· Select the desired data set to use from the "Data set list"

· (Optional) To know if selected data set maps the objects correctly, or as desired, click on the "Display Field Mapping" button

· Click the "Inject" button.

Note: if errors occur with step 9 and/or 10, confirm correct headers/field names used on data set’s (check notes from step 2)

Permissions required to run a Test in Sprinter

You must have the following permissions in Application Lifecycle Management (ALM) to run a test in Sprinter:

Permission > Permission Level

Test Lab > Results Create, update, and delete

Test Lab > Run Create and update

To save your user information to ALM you need the following additional


Permission > Permission Level

Resources > Resource Create, update, and delete

Resources > Resource folder Create and update

To edit test steps, you need the following additional permissions:

Test Plan > Design Step Create, update, and delete

To create new manual tests, you need the following additional permissions:

Test Plan > Test Create, update, and delete

Test Plan > Test Folder Create, update, and delete

Test Plan > Test Parameters Create, update, and delete

Quality Center (QC) / Application Lifecycle Management (ALM) client components files download

It is known that first time a user connects to a Quality Center (QC) / Application Lifecycle Management (ALM), either via Internet Explorer or another client tool, the required client components files get downloaded, but what other scenarios trigger the re-download of such components, after the first time

Download situations

The mentioned files get analyzed and downloaded, each time ALM Platform is updated. This updating scenarios include the following cases:

A patch is installed.

An extension is installed.

A new test type is created.

ALM Platform configurations are changed.

Background behavior

It is possible that not all files are download, only those not matching ones offered by QC / ALM server (including if client has newer / higher version of a file, is different, so it must be updated).


This task (download of components), requires:

End-user to have full admin rights,

User Account Control (UAC) is Off.