/build/static/layout/Breadcrumb_cap_w.png

HP QuickTest Professional

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 3.6k  |  Created: 09/11/2009

Average Rating: 0
QuickTest Professional has 1 inventory records, 1 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (5)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 3 / 5 (Average) based on 1 ratings
Most Commonly Reported Deployment Method
Windows Installer with Custom Transform (MST)
2
Note
If you need to configure the installation with a licence server, here some tips :

Environment variable
LSHOST=Your_Licence_server_IP

[HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\QuickTest Professional\Rainbow]
"LicType"=dword:00000001

A batch file needs to be edit to remove the demo licence installation.
Edit Run_before_finish.bat and REM the following line : (line 308)
if exist bin\instdemo.exe bin\instdemo.exe -silent -CheckConcurrentLicenseExist
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
2
Note
On startup there is a dialog box that comes up offering a link for more info on SOA testing capabilities. This prompt can be switched off with the following key:

[HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\QuickTest Professional\MicUISettings]
"HideWSInformationMessage"=dword:00000001

To turn off automatic updates:
[HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\QuickTest Professional\MicTest]
"CheckForUpdates"=dword:00000000
"SaveMdrvFiles"=dword:00000000

To turn off an add-in:
[HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\QuickTest Professional\MicTest\AddIn Manager\Terminal Emulators]
"Active"=dword:00000000

This add-in was throwing a message on startup for me saying that HLLAPI.DLL could not be found.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
0
Virtualization
Today I mapped out some issues with sequencing HP QuickTest Professional 10.0...

As we haven't performed UAT there may come back other areas where we hit other problems, but to at least sequence this I had to perform the following;

In the folder Quicktest\MSI\ locate run_before_finish.bat and uncheck that its Read Only.
Locate;
if exist bin\instdemo.exe bin\instdemo.exe -silent -CheckConcurrentLicenseExist
and comment it (as an example);
REM if exist bin\instdemo.exe bin\instdemo.exe -silent -CheckConcurrentLicenseExist

Of course there has to be some type of licensing - the one we use is dependt on concurrent license and therefore measured by a license-server.
If the above command was allowed to run it would BSOD the sequencer.

This problem didn't seem to occur with the 4.6 RC2 release, however my sequencer was a 4.5 RTM.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
0
Note
When repackaging QTP you have to automate the installation of the BB Capture Driver.

The BB Capture Driver can't be installed via DPInst nor DIFxApp because this is a non-PNP driver.
In order to get the work done correctly you must use the DevCon command-line utility.

First you have to put all related driver files in one directory (eg for example %ProgramFiles%\HP\QuickTest Professional\CaptureDriver).
These files are:
bbcap.dll
bbcap.inf
bbcap.sys
bbcap_ntx86.cat
bbchlp.dll
and the DevCon utility devcon.exe

The devcon utility has problems when directly using it via a Custom Action.

In order to install the driver correctly you have to build a WiseScript or a VB Script for that matter (e.g. VB Script also needed when using InstallShield instead of Wise).
One script for installing the driver and one for removing the driver.

Use the following commandline parameters for installing the driver (as an example the CaptureDriver folder will be used)

%ProgramFiles%\HP\QuickTest Professional\CaptureDriver\devcon.exe install bbcap.inf BB_Capture_Driver

Use the following commandline for removing the driver (as an example the CaptureDriver folder will be used)

%ProgramFiles%\HP\QuickTest Professional\CaptureDriver\devcon.exe remove bbcap.inf BB_Capture_Driver
After removing the following files still exist:
%SYSTEM32%drivers\bbcap.sys
%SYSTEM32%bbchlp.dll
%SYSTEM32%bbcap.dll
%WINDIR%\Inf\oem??.inf (where ?? is the randomly generated number of the BB Capture Driver file)

Remove all files
The oem??.inf file can be removed if you do a check upon values within the inf file (for example "; bbcap.inf" without quotations) and when this value exist you can safely remove it, otherwise keep this file where it is.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
-2
Command Line
When installing the paldrv driver use the following parameters.

Install pal_drv:
%ProgramFiles%\hp\QuickTest Professional\bin\nt_tr.exe /REGSERVER

Uninstall pal_drv:
%ProgramFiles%\hp\QuickTest Professional\bin\nt_tr.exe /UNREGSERVER

Following also can be used within a Custom Action if you've repackaged QTP.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

QuickTest Professional

Version

10.00.0000

Contact

HP

Uninstall String

MsiExec.exe /I{4CC41272-6AA9-4946-ABA6-61C05A40DE80}

Questions & Answers (1)

Questions & Answers related to HP QuickTest Professional

Blogs (0)

Blog posts related to HP QuickTest Professional

Reviews (0)

Reviews related to HP QuickTest Professional

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ