White Papers
Abstract
IBM Rational Integration Tester (RIT) is an integration testing and application (service) virtualization tool formerly named Green Hat. RIT is part of the Rational Test Workbench offering and it enables:
1. Continuous Integration Testing
2. Test Virtualization
Whereas, HP Quality Center, a test management tool is now popularly known as Application Life Cycle Management Tool(ALM) as it is no longer just a test management tool but it supports various phases of the software development life cycle. HP-ALM, an enterprise-wide application that is based on Java 2 Enterprise Edition (J2EE) technology and uses MS SQL Server or Oracle as its back end.
In this article, you would look into how both RIT and HP-QC can be integrated, delivering a stronger Integration testing capability.
Content
Author: Rajesh Avanthi
Table of Contents:
RIT’S CUSTOMTYPE FILES REGISTRATION
Introduction
IBM Rational Integration Tester (RIT) is an integration testing and application (service) virtualization tool formerly named Green Hat. RIT is part of the Rational Test Workbench offering and it enables:
- Continuous Integration Testing
- Test Virtualization
Whereas, HP Quality Center, a test management tool is now popularly known as Application Life Cycle Management Tool(ALM) as it is no longer just a test management tool but it supports various phases of the software development life cycle. HP-ALM, an enterprise-wide application that is based on Java 2 Enterprise Edition (J2EE) technology and uses MS SQL Server or Oracle as its back end.
In this article, you would look into how both RIT and HP-QC can be integrated, delivering a stronger Integration testing capability..
Installation Overview
In this article, you would be focusing on the server side distribution of QC installation along with the client only installation. The client only distribution also contains a smaller package of server component built within it.
The difference between the server side installation and the client only installation is that with the server distribution installation, when the client logs into HP-QC they can automatically download the RIT integration files along with the QC client components. On the other side when the QC client only installation is carried out, you need to manually configure the integration setup.
Rational Integration Tester provides four different files, specific to different versions of HP-Quality Center. The default location of these QC files is located under:
C:\Program Files\IBM\RationalIntegrationTester\tools\HP
Server Side Installation
Let's proceed with the server side installation here. You need to copy the QualityCenterServerDist1.zip file onto the QC server machine at any given location. Once the copy process is completed, you need to identify the default deployment location for HP Quality Center. The default QC deployment root directory would be located under C:\ProgramData\HP\ALM\Application
Now, unzip the QualityCenterServerDist1.zip file which was copied on to the QC server machine. Upon unzipping, you see the following files within it.
Copy only the “CustomTestTypes” and “Extensions” folder and place it under C:\ProgramData\HP\ALM\Application\20qcbin.war
After copying these two folders, the next step is to ensure that the ALM server is stopped (Red X mark appearing on the ALM icon). In order to stop the ALM server, you see the ALM icon within the system tray section on the screen as shown below.
Now, you need to re-deploy these files with the integration files using the “Server Deployment Wizard”. You can invoke the deployment wizard by clicking on “Start” >> “ HP ALM Platform” >> “Server Deployment Wizard” as shown below.
The Server Deployment Wizard gets invoked, with the welcome page as shown below:
All you need to do here is click “Next” button and that should re-deploy the application
Once the application is re-deployed, it would prompt whether you want to start the ALM platform.
Click “Finish” and that should start JBOSS . As soon as this process gets completed, you see that the default browser (Generally Internet Explorer) gets opened up automatically, loading the QC homepage
On this homepage, click on “Site Administration” link, which loads all the relative components. As soon as the QC components get loaded, it prompts for the login credentials. Upon login, you see the below user interface.
Click on ”Tools” >> “Update Test Types”. Basically the integration provided by RIT here is a custom test type (GH-Test). Clicking on the “Update Test Types” would ideally synchronize all the changes that were made to the Test Type definition files within 20qcbin.war folder.
Click “Yes” and that should prompt a message saying that all active projects are updated. You can now login to client access HP Quality Center.
Client Side-Only Installation
For the client side-only installation, you need to perform the below on the QC server end.
1) On the server, navigate to the C:\ProgramData\HP\ALM\Application\20qcbin.war
2) From the "GHTestQC11Integration.zip folder, copy only the "CustomTestTypes" folder on to the "20qcbin.war" folder (Default deployment folder for HP-QC).
Notice that you do not need to copy the "Extensions" folder as done earlier. But if you look at the "CustomTestTypes" folder, you see only the "GH Tester.ini file, containing a class identification value (CLSID).
The custom Type name here is “GH-Tester”.
Once the “CustomTestType” folder is copied, you need to invoke the “Server deployment Wizard” as stated earlier and re-deploy the entire application. Once the application re-deployment process gets finished, click on “Site Administration” to update the “Custom Test Types”. This sets the minimal server side configuration and now you are ready to get the client side configured for this integration. For this to be done, launch the browser (Internet Explorer in this case) with Administrator rights for the first time and then login to (
QCServer:8080/qcbin/start_a.jsp[ ). Now locate where the QC client files are saved on your machine. For Example, in this case, the QC client files are located under "C:\Users\IBM_ADMIN\AppData\Local\HP\ALM-Client. At this location you should now be able to see the server related folder to which you are connected to. It can also be a localhost folder, depending on the way the server and client deployments are setup
NOTE: The server name to which the QC client is connected to is “ghserver10” as shown in the above snapshot.
Navigate back to the Rational Integration Tester directory and copy all the files present within the QualityCenterServerDist1-client-only.zip folder.
Copy the above files on to the QC client directory (C:\Users\IBM_ADMIN\AppData\Local\Hp\ALM-Client\<<Server Folder>>).
RIT CustomType Files Registration
After copying these files into the QC client's server folder, you need to register these files. In-order to register these files, you need to run a script. Launch Command Prompt with "Run as Administrator" option and navigate to the QC client folder as shown below. You can as well see if the RIT files are copied correctly.
To register these copied files, simply execute the batch file named "RITIntegrationSetup.cmd". This batch file by default is located within the ALM-client's server folder.
That’s all and you are done with the integration setup between RIT and HP-QC.
Test Execution
You can create a Test Plan with QC that will link to Rational Integration Test. For this, you can select the "Test Plan" view under QC and select "New Test" as shown below
Specify the test name and select the type as "GH-Tester".
From the test that was created, select "Test Script" tab to add the resources specific to Rational Integration Tester. The test script screen does appear which is the part of RIT integration code here.
Click “Select” and that should bring up the resources present within the active running instance RIT project.
If incase there exists no running instance of RIT, then you would see all the projects listed within the “Resource Selection” dialog.
The selected test is then made to put into a "Test Set". The Test set acts as a container holding multiple Tests (similar to TestSuite concept). In-order to create a TestSet, navigate to "Test Lab" section in QC and click "New Test Set" as shown below.
Once the TestSet is created, you need to add the tests that were selected from the "Resource Selection" window earlier. Click on the "Execution Grid" tab and select "Select Tests". This should bring up the Test Plan Tree containing the selected Tests. Drag and drop these relevant Tests from the "Test Plan Tree" section on to the "Execution Grid" pane.
For the test to execute, you need to specify the location, where the RIT instance is hosted and running. It could be a case where RIT and HP-QC client is configured on the same machine, and you specify the tests to be executed with “Localhost” selected.
In a case where RIT is installed on a remote machine, specify the remote host location details for test execution. The test execution process involves DCOM inorder to execute the tests.
The next step is to configure the RIT environment for the selected tests. To set the environment, you can double click on the test and that should bring up the “Test Instance Details”. Select “Execution Settings” >> “Automated” as show below.
Execution Methods
From the “Test Instance Details” dialog, select one of the available environments. There are 2 modes of execution methods:
- Running Test Instance
- Command Line (Legacy)
The “Running Test Instance” execution method is the latest addition to increase the performance factors involved in the test execution process.
In the “Command Line” execution method selection, this starts an application present with the RIT installation directory called "MercuryTest.exe". Basically this starts the tester with no User Interface (UI), loads the project and then runs the tests. Once the Test execution gets completed, it closes the project. This entire process is repeated for each of the tests that are loaded within the TestSet. This process is very much time consuming.
The test execution status gets reflected along with the run report data as shown below:
For each of the test executions, you can set the log levels. The default mode is selected as “Debug” which captures the entire execution process. Setting the log level with “Debug” creates a log file (GHRunAgentOutput_1.log) within the relevant login profiles “Temp” directory.
This is how the GHRunAgentOutput_1.log data would appear.
TIPS
In rare scenarios, the RIT’s component files are not get registered correctly, you may manually run the RITIntegrationSetup.cmd batch file to get these files registered. Also to validate if RIT custom Type files are part of any selected project, you can navigate to the QC server machine and log into Site Administration section.
Expand the relevant project and look for the table named “ ENTITY_SUBTYPES”. This table should reflect the custom types provided by RIT.
There is another configuration that needs to be setup inorder to execute the RIT scripts from within Quality Center. This is only required when working with HP Quality Center v11 . In-order to make the RIT application to use the TD connection library, you need to install the add-in for HP-QC. There are 2 ways to configure this add-in
1) From the QC home page (QCServer:8080/qcbin), click "Add-Ins Page" as shown below
. 1) Login to ALM (Shown in above screenshot). Click “Help” >> “Add-Ins Page”.
With both the above options, you land up with the “Add-Ins page” as shown here. Click the option named “HP Quality Center Connectivity”
This should bring up the QC connectivity Add-In page with the “Download Add-in” link.
Clicking on the “Download Add-in” link should download the “TDConnect.exe” . Click “Run”
This would download the executable file and install the same.
NOTE: This Add-In should be installed regardless of whether you configure client –only install or the Server install.
References
http://pic.dhe.ibm.com/infocenter/rithelp/v8r5m0/index.jsp.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS DOCUMENT, IT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS DOCUMENT OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS DOCUMENT IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REDOCUMENTS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS OR SOFTWARE. |
|---|
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27042585