Quality Center integration with Selenium Webdriver

Introduction to HP Application Lifecycle Management/Quality Center:

HP ALM formerly known as Quality Center is a Test Management tool to manage entire Quality Assurance and testing process for an organization. Before being called HP Quality center it used to be Mercury Test Director.

ALM helps make project management, from requirements to deployment easier. It increases predictability and creates a framework to manage projects from a central repository.

 
Selenium Webdriver :

Selenium WebDriver is a tool for writing automated tests of websites. It aims to mimic the behaviour of a real user, and as such interacts with the HTML of the application. Selenium WebDriver is the successor to Selenium RC. Selenium WebDriver accepts commands (sent in Selenese, or via a Client API) and sends them to a browser. This is implemented through a browser-specific browser driver, which sends commands to a browser, and retrieves results Selenium 2.0 aims to provide a basic set of building blocks from which developers can create their own Domain Specific Language.

Integration framework using selenium:

The proposed automation framework has been developed to integrate the Selenium with Quality Center and the integration concept can be used with any other open source functional automation tool with QC.

The overall costs associated with automation are minimized by the use of Open Source tool with Quality Center compared to using QTP tool with Quality Center. Using of selenium with QC supports the execution of test scripts with Standard test management tool. Some of the key benefits of the proposed framework are

a) No cost associated with the Functional Tool

b)  Use of Selenium Webdriver ensures that the automated script can be developed in the language in which resources are available within the organization

c)  Support available in the form of plenty of online forums

Integration Procedure:

Pre-requisite before starting the scripts are 
       a.    Selenium-Server-Standalone.Jar – To support Webdriver API
       b.    Com4j.jar – To interact with QC Login Webpage
       c.    otiClient.jar – To interact with QC components page


Step 1 : Conversion of OTAClient.dll into Jar file - which required to interact with QC folder structure


Step 2 : How to use QCIntegration Class file in your selenium program to interact with QC operations. 

In ALM/QC,
Create a test case with the name “TestCase01” in the test set “TestSet_01” 
(Test case is to verify the webpage title after Google search)

The execution workflow of our selenium script is,

     When the user executing the Script file (eg: TestCaseOne.java) with respect to the test case, the webdriver opens the web browser and performs the steps mentioned in the program & update the test results in QC using QC interacting script file (QcIntegration.java). 

 


 

Popular posts from this blog

Selenium Webdriver Interview Questions with Answer

Selenium IDE Interview Questions with Answer

DLL to Jar file conversion