LISA QC/ALM Integration
System Requirements & Pre-Requisites
System Requirements
LISA Quality Center/Application Lifecycle Management Plug-in is compatible to both
32-bit & 64-bit LISA Workstation software (instead of only on 32-bit version).
It has been tested and certified that LISA QC/ALM Plugin will work on a 64-bit
Machine with 32-bit LISA, 32-bit browser and 32-bit JVM but it will not work in a 64bit browser or with a 64-bit JVM or 64-bit LISA. The process needs to run in 32-bit
mode only.
If you have a 64-bit machine, with 64-bit LISA and/or 64-bit JVM, your test LISA cases
will not run with the QC/ALM plugin. This is not supported as this is a limitation with
HP.
QC/ALM does not support running in anything other than 32-Bit browsers. The same
OCX files that get loaded when you access the QC/ALM site are the same files that are
packaged in the QC/ALM Connectivity Components that we require for our plugin.
2
System Requirements & Pre-Requisites (continued)
System Requirements
You need to make sure the following 2 Add-ins are installed from QC/ALM:
HP Quality Center Connectivity
HP ALM Client Registration (Register HP ALM Client)
See the supported platforms page https://hpln.hp.com/page/alm-qc-enterprisetechnical-specifications and search for “Desktop Client Supported Environments”. You
can see the list of supported browsers and the NOTE about how things work. Until HP
has a solution that allows us to run in a 64-bit mode on a desktop client, we will not
be able to support a 64-bit plugin.
3
System Requirements & Pre-Requisites (continued)
System Requirements
• Browsers Supported
o Microsoft Internet Explorer 8 32-bit
o Microsoft Internet Explorer 9 32-bit
o Microsoft Internet Explorer 10 32-bit
• .NET 2.0 Runtime
• 32 bit version of LISA.
• 1 additional Workstation / Server License needed
• Microsoft Windows is only supported with the plugin for QC/ALM
• LISA 7 requires Java 1.7.x (32 bit)
4
LISA Integration with
QC -10 / ALM - 11
LISA Configuration
Standalone vs. Distributed
Standalone Configuration
• All LISA components exist on the same physical system.
• All LISA components share the same properties files.
Distributed Environment
• Major LISA components are distributed across many physical
machines.
• Many clients (LISAWorkstation) connect to the distributed LISA
components.
• Primarily used in large enterprise environments with many
developers.
6
Configuration – LISA Components
Enterprise Deployment – Registry
Registry
• The registry keeps track of the locations of any LISA runtime components and
provides lookup to their locations for each registered component.
The fully qualified name of the registry is tcp://hostname-or
Ipaddress:2010/registryname
For example:
tcp://localhost:2010/Registry
tcp://myserver:2010/Registry
• If LISAWorkstation & Registry are on different machines , you need to specify the
registry url property in the local.properties file of the Workstation Machine
lisa.registry.url=tcp://<ipaddress> :2010/Registry
7
Configuration
Enterprise Deployment – Coordinator & Simulator
Coordinator Server
• The default name of a coordinator server is set by the lisa.coordName property.
• lisa.coordName=Coordinator
The fully qualified name of a coordinator server is:
tcp://hostname-or-IPaddress:2011/coordinator-name.
Simulator Server
• The default name of a coordinator server is set by the lisa.SimulatorName property.
• lisa. SimulatorName=SIM1
• The fully qualified name of a coordinator server is:
tcp://hostname-or-IPaddress:2014/Simulator-name.
For test cases:
If a coordinator is running, then it will be used to run the test case.
If a coordinator is not running, then the Test Runner utility will be used to run the test
case locally.
For MAR files and MAR info files:
If the file specifies a coordinator, then the coordinator must be running.
If the file does not specify a coordinator, then the plug-in creates and starts a local
coordinator.
8
Configuring Quality Center 10 / 11 Instance
• The first time you access QC link you would be asked to
download 2 Quality Center/ALM add-ons to your machine. This
is required to Integrate QC/ALM with LISA. Please make sure you
follow the instructions as you are prompted. This is normally
done on the LISA Workstation machine.
HP Quality Center Connectivity
HP ALM Client Registration (Register HP ALM Client)
9
Quality Center 10 Home Page
• Login to QC.
10
ALM 11 Home Page
• Login to ALM.
11
Installing the QC-Plugin
In order to install and use iTKO LISA’s Quality Center plug-in, the following system
prerequisites must be met:
•
An install of LISA
• Access to HP's Quality Center 10.0 or above
• An install of the .NET 2.0 runtime
• An install of both QC/ALM Add-ins
• For Lisa 7 and up, td_plugin.exe, is shipped with Lisa . Look under
LISA-HOME\addons\qc folder .
12
Configuration
Key Points about QC Plugin
• Run td_plugin.exe installer into your LISA-Home folder.
• Once installation is done, the following files will be added to
your Lisa-Home/bin.
13
Linking LISA Test to
QC/ALM
Linking LISA Test to QC/ALM
• The LISA plug-in relies on the VAPI-XP test type to integrate with QC/ALM. In order to link a
QC/ALM test to LISA, using the "Test Plan" feature of QC/ALM, create a new test. When
prompted, select VAPI-XP from the dropdown and give the test a name, then click OK.
Choose the scripting language you would like to use and then click Finish because you will
be adding the script yourself in a later step.
15
Usage:
• You can pick any scripting language you want (VBScript or JavaScript )
and click Finish.
• Once the test is created, click on the Test, select the 'Test Script' tab of
the newly created test and replace the default contents with the
contents of the appropriate script template located at
Start>Programs>Lisa>Quality Center Plug-in><<*Script Template>>
16
Usage:
• Once the test is created, click on the Test, select the 'Test Script' tab of
the newly created test and replace the default contents with the
contents of the appropriate script template located at
Start>Programs>Lisa>Quality Center Plug-in><<*Script Template>>
• Copy the Script from :
Start ->Programs ->LISA ->Quality Center Plug-in -><<*Script Template>>
JavaScript or VBScript template
To : Test Script Tab
17
Usage:
18
Attaching Lisa Test to QC/ALM
After the script template has been added, the final step is to add references to the test, staging and config files
in the Attachments tab. It is recommended that the test, staging and config files be added as links (URL) rather
than attaching the actual file itself. This will allow for any changes to the LISA test to not have to be uploaded
back to QC/ALM. To do this, choose the link icon and then file a properly constructed URL to the file. If the file is
on the same machine as the QC instance, it should be in a form similar to this :
file:///<drive>:/<path>/<file>.<ext>
Test Doc: file:///c:/Lisa/Projects/Tests/logTest.tst
Staging Doc: file:///c:/Lisa/Projects/StagingDocs/1User1Cycle_ManyMetrics.stg
Config: file:///c:/Lisa/Projects/Configs/project.config
If the file is on a Share-drive :
file://///w2008svr3.itko.local/Shared/QCTests/5.0tests/Lisa_config_info.tst
The LISA test can be a test case file, a MAR file, or a MAR info file.
For test cases, you can also attach a staging document and a configuration file. If you do not attach a staging
document, then a staging document is automatically created with these characteristics:
One user, One cycle, Zero think time
For MAR files and MAR info files, you cannot attach any additional files.
19
Running Test from Test Plan– Debug Mode
The test is now ready to be run from the "Test Plan" debug window. If the file is linked
(recommended), then you can be sure that any changes to the test will first be updated
before the test is run. To run the test from the Test Plan (debug mode), locate the test and
click on the Test Script tab. From there you can click the green arrow (Execute Script). The
test will start executing, and its output will show up in the output window below. You will
be notified once the test is completed.
20
Running Test from Test Lab
• To run the test from the Test Lab, Click on the Test Lab Icon on your right
panel. Create a Test Set, say Lisa Tests
• Click on the ‘Select Tests Tab ’ in the Top Menu bar. (see below), and the
Test plan tree opens on your right.
• Using the Green arrow in the Test Plan Tree, Add the test to a valid test set
and from there you can then either run the single test or the entire test set.
Once the test is done running, you can check the status of the test from the
Test Set window or check the test's history in the Test Instance Properties
window.
21
Test Results
The following image shows the results from a run of the rest-example
test case in the Test Lab.
22
(
LISAQCRunner Command-line interface
The LisaQCRunner executable in the LISA_HOME/bin directory lets you run Quality
Center LISA tests from the command line
This executable has the following format:
LisaQCRunner [-h <host>] [-P <port>] [-u <user>] [-p <password>] [-D <domain>] [-l <project>]
run|debug|reload <testname>|all
run
Runs the test name that you specify as an argument. The output appears in the command window. The results are persisted in Quality Center.
debug
Runs the test name that you specify as an argument. The output appears in the command window. The results are not persisted in Quality Center.
reload
Reloads the test name that you specify as an argument, or all LISA tests (if the argument is all).
Example:
LisaHome/bin> LisaQCRunner -h machine.example.com -P 8080 -u admin -p mypassword -D DEFAULT -l myproject run
RunWithTestandStage
Connecting...
Connected
Running RunWithTestAndStage with the following parameters:
Test Doc: file:///c:/lisa/examples/tests/rest-example.tst
Staging Doc: file:///c:/lisa/examples/stagingdocs/1user1cycle0think.stg
Config:
23
Quality Center Plug-in Troubleshooting
• To improve performance, the LISA bridge always keeps a reference to the LISA
COM server so that it does not need to be instantiated for each API call. When
the process hosting the bridge terminates, this reference is released unless
the host is a native app like a web browser so the LisaQCRunner.exe process
will stay alive. This is normally not a problem unless something gets in a bad
state (for example, because of an abrupt termination). In that case, consider
manually terminating the lingering LisaQCRunner.exe process before
proceeding.
24
Common issues that arise with QC and Lisa
•
•
•
•
•
•
•
25
In the vast majority of cases with LISA the primary cause of most issues is:
Licensing or connection (network, firewall etc) issues. QC-plugin require one
additional license to run tests.
User downloads the wrong version of the plugin. Cannot load Main class() error
User running the test may not have permission to Run VAPI-XP Test in QC Test Lab vs
Test Plan. Check with Admin for Permission issue.
Connectivity issues between LisaWorkstation and Remote Registry.
add the below property in your local.properties file on the Workstation machine.
lisa.registry.url=tcp://<ipaddress> :2010/Registry
Verify file attachment format in Test Plan. The user may be using the wrong format.
No space allowed for file path or project or file name. ( eg: Document and Settings)
If the Test does not run in QC, first verify that the Same test runs fine using Test
Runner Command. Then Run using LisaQCRunner command line tool.
You cannot run a Lisa Test Suite in QC, only individual tests or you could create a Test
Set in QC TestPlan and then run the whole TestSet.