2 System Requirements & Pre-Requisites 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 64-bit 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.
3 System Requirements & Pre-Requisites (continued) You need to make sure the following 2 Add-ins are installed from QC/ALM:HP Quality Center ConnectivityHP ALM Client Registration (Register HP ALM Client)See the supported platforms page https://hpln.hp.com/page/alm-qc-enterprise-technical-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.
4 System Requirements & Pre-Requisites (continued) Browsers SupportedMicrosoft Internet Explorer 8 32-bitMicrosoft Internet Explorer 9 32-bitMicrosoft Internet Explorer bit.NET 2.0 Runtime32 bit version of LISA.1 additional Workstation / Server License neededMicrosoft Windows is only supported with the plugin for QC/ALMLISA 7 requires Java 1.7.x (32 bit)
6 LISA Configuration Standalone vs. Distributed Standalone ConfigurationAll LISA components exist on the same physical system.All LISA components share the same properties files.Distributed EnvironmentMajor 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.
7 Configuration – LISA Components Enterprise Deployment – 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/registrynameFor example:tcp://localhost:2010/Registrytcp://myserver:2010/RegistryIf LISAWorkstation & Registry are on different machines , you need to specify the registry url property in the local.properties file of the Workstation Machinelisa.registry.url=tcp://<ipaddress> :2010/Registry
8 Configuration Enterprise Deployment – Coordinator & Simulator Coordinator ServerThe default name of a coordinator server is set by the lisa.coordName property.lisa.coordName=CoordinatorThe fully qualified name of a coordinator server is:tcp://hostname-or-IPaddress:2011/coordinator-name.Simulator ServerThe default name of a coordinator server is set by the lisa.SimulatorName property.lisa. SimulatorName=SIM1tcp://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.
9 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 ConnectivityHP ALM Client Registration (Register HP ALM Client)
12 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 LISAAccess to HP's Quality Center 10.0 or aboveAn install of the .NET 2.0 runtimeAn install of both QC/ALM Add-insFor Lisa 7 and up, td_plugin.exe, is shipped with Lisa . Look underLISA-HOME\addons\qc folder .
13 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.
15 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.
19 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.tstStaging Doc: file:///c:/Lisa/Projects/StagingDocs/1User1Cycle_ManyMetrics.stgConfig: file:///c:/Lisa/Projects/Configs/project.configIf the file is on a Share-drive :file://///w2008svr3.itko.local/Shared/QCTests/5.0tests/Lisa_config_info.tstThe 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 timeFor MAR files and MAR info files, you cannot attach any additional files.
20 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.
21 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 TestsClick 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.
22 .Test ResultsThe following image shows the results from a run of the rest-example test case in the Test Lab.
23 LISAQCRunner Command-line interface (LISAQCRunner Command-line interfaceThe LisaQCRunner executable in the LISA_HOME/bin directory lets you run Quality Center LISA tests from the command lineThis executable has the following format:LisaQCRunner [-h <host>] [-P <port>] [-u <user>] [-p <password>] [-D <domain>] [-l <project>] run|debug|reload <testname>|allrunRuns the test name that you specify as an argument. The output appears in the command window. The results are persisted in Quality Center.debugRuns the test name that you specify as an argument. The output appears in the command window. The results are not persisted in Quality Center.reloadReloads 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 u admin -p mypassword -D DEFAULT -l myproject run RunWithTestandStageConnecting...ConnectedRunning RunWithTestAndStage with the following parameters:Test Doc: file:///c:/lisa/examples/tests/rest-example.tstStaging Doc: file:///c:/lisa/examples/stagingdocs/1user1cycle0think.stgConfig:
24 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.
25 Common issues that arise with QC and Lisa 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() errorUser 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/RegistryVerify 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.