When QuickTest Professional (QTP) or HP Sprinter and java application (for example Lotus Notes Client 8.5.1) are installed on the same machine, even if QTP or Sprinter is not used to test Lotus Notes we see that Lotus Notes application will crash unexpectedly on startup.
Prevent the Java agent from injecting in the Java Virtual Machine (jvm):
Find the process name of the application that is crashing (shown in the Task Manger). For example "notepad.exe"
Go to Registry (Start>Run>regedit)
Navigate to registry key: "HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\JavaAgent\Modules"
Note: On 64 bits operating system, locate path under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mercury Interactive\JavaAgent\Modules
Create a DWORD value with the same name as the process name of application.
Set the value as "0"
Note: The above steps only apply to application that run with .exe (if it’s a jar or bat file, the suggestion will not work).
After creating and running a test, an error is displayed "Cannot open the run results because the HP Run Results Viewer is not installed on this computer"
QuickTest Professional (QTP) / Service Test (ST) / Sprinter version 11 introduced a new reporting tool called HP Results Viewer. Some other products such as LoadRunner may be using this tool as well.
Unlike previous versions, its installation process automatically happens after the core product related to it get installed on a visual-less, invisible/on-background process which only get noticed as soon as the shortcut icons on desktop, among other things, gets placed. The QuickTest Add-in for Quality Center also makes use of this tool, and its installer (when used on machine without QTP) performs this reporting tool’s installation when finished on background.
Note: This new reporting tool, has separate installers on the core product disc
· Ensure the following registries, folders and files get created on the machine once the core product finish its installation:
Folder: C:\Program Files\HP\Run Results Viewer
Desktop Shortcut: "HP Run Results Viewer.lnk"
HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\Test Results
HKEY_CURRENT_USER\Software\Mercury Interactive\Test Results (generated after opening)
· If the core product was installed properly, simply run directly the HP Results Viewer installation files:
QTP: <Installation files>\RunResultsViewer\<Language>\setup.exe
ST: <Installation files>\STSetup\MSI\ThirdPartyInstallations\HP_Run_Results_Viewer.msi
The ALM 11 tool denominated as "Sprinter" currently supports the following virtualization environments/technologies and versions:
- VMware WorkStation: 5.5, 6, 7
- VMware ESX: 4, 4.1
Note: Any major (i.e. VMware Workstation 5) and minor (5.5) versions are displayed as separate items.
If a version isn’t displayed, it needs to be considered non-quality-assured therefore not officially supported by the product. Note: There are versions not listed above, which may work however still not quality-assured.
Below are the limitations when working with Google Chrome browsers
· Recording steps in Google Chrome is not supported
· The following methods are not supported
· Running steps in the following scenarios is not supported:
o chrome://* pages
o Multiple tabs
o Multiple browsers
o Web pages that include frame sets or Chrome Frames
o WebXML test objects
o Web test objects located inside iFrame controls with a ‘blank’ or ‘about:blank’ SRC identification property value
o Developer Tools pane (Running steps on Google Chrome while the Developer Tools pane is open is supported.)
o Web 2.0 test objects or Web Extensibility-based test objects
o Web-based environments, such as SAP Web, Siebel, Java, .NET WebForms , and so on
· Chrome embedded browser process
· Embedded Chrome controls
· Google Chrome Plug-in. Note: The Internet/Firefox add-on/plug-in to load Chrome Frames
· Dialog Popup recognition. Note: For more details see Document ID KM00494510 – QTP/UFT does not recognize Popup Dialogs in Chrome Browser
Google Chrome browser currently uses Automatic Updates, which may automatically upgrade browser to unsupported version.
Workaround: In order to disable the auto updates you can refers to the Google documentation: