WIXLIB

IKAN ALM andHP ALM/HP Quality Center EnterpriseWhere Development, Testing and Operations meet

Table of contentsExecutive summary. 3Problem statement. 4Solution Description. 4The IKAN ALM Issue Tracking System plugin (HPQcITSPlugin) for HP ALM/HP . 5Quality Center Enterprise. 5The HP Quality Center TestRunner (HPQcTestRunner). 5Benefits. 6Implementation scenario. 6The IKAN ALM Issue Tracking System plugin (HPQcITSPlugin) for HP ALM/HP Quality Center Enterprise. 6The HP Quality Center Issue Tracking System plugin (HPQcITSPlugin). 8Architectural components used for this solution. 9Summary/Conclusion.11For more information. 122Where Development, Testing and Operations meet

Executive summaryApplication Lifecycle Management (ALM) is a key discipline aimed at managing the entire softwaredevelopment process from requirements through deployment, involving Business Analysis, ProjectManagement, Development, Quality Assurance (QA), and Testing and, finally, the delivery of the resultsto Operations.The trend toward globalization (distributed teams), evolving development methodologies (fromWaterfall to Agile), the omnipresent budget restrictions and the necessity to deliver more applicationsfaster, increase the need to automate the complete ALM process in order to:3 Make the ALM process enforceable3 Improve communication between all stakeholders3 Enhance closer collaboration and teamwork3 More efficiently use the appropriate development, testing and operations resources3 Deliver applications faster and with higher quality3 Reduce the overall cost and increase the efficiency of application development anddeliveryIKAN Development, an HP Gold EMAP Partner, provides an end-to-end ALM solution to our clientsleveraging HP ALM/HP Quality Center, the ultimate goal to apply enterprise-wide ALM standards, willprovide higher quality applications, in less time and at lower cost.This White Paper targets all parties technically interested in ALM, be it executives, technical managers,software architects, operations people or developers.Where Development, Testing and Operations meet3

Problem ation development and delivery processesthe missing link to enable fully integrated defecttracking between the two solutions.do not automatically link up the activities of theQA and Testing people with the activities of theAnother area which may need improvement isDevelopers. For example, defects identified bythe triggering of automated tests that are storedthe QA and Testing department and stored in ain HP ALM or HP Quality Center Enterprise. Beforestandard repository such as HP Quality Centernow, a developer committed his code and theEnterprise/HP ALM, may not be automaticallydefect tracking number(s) with comments intolinked to the concerned development cycle.the VCR (Version Control Repository), and theBuild process linked the Defects to a Build. Next,On the other hand, when Developers release athe QA and Testing department could executenew cycle to the QA and Testing department,the automated tests stored in HP ALM/HP Qualitythe status of any reported Defectsmay notCenter and communicated the results to thebe automatically synchronized and the newlyDevelopment department. The HPQcTestRunnerdeveloped code – whereby Defects are fixedfrom IKAN Development provides an answer to–and may not be available to the QA and Testingthis inefficient way of working by systematicallypeople in a transparent and coherent way.triggering the automated tests as part of the fullyautomated Build or Deploy process in IKAN ALM.This lack of integrated tracking of Defects resultsin redundant communication efforts trying toThe advantage is two-fold: the developerfind out the overall status of the Defects: whichimmediately receives feedback on the successfulDefects are solved by which Builds, where can Ior unsuccessful execution of the tests, and thefind the different Builds and how do I install them?QA and Testing department gains precious timeFurthermore, it slows down the developmentby not having to launch the tests manually.process and increases development costs due tothese communication problems. For customersNote: For the remainder of this document, we willwanting to integrate defects between IKAN ALMuse the term “Defect” to refer to both Defectsand HP ALM/HP Quality Center Enterprise, the(HP ALM/HP Quality Center Enterprise) and IssuesHPQcITSPlugin from IKAN Development provides(IKAN ALM), except for when it is part of a name.Solution Description4Where Development, Testing and Operations meet

The IKAN ALM Issue Tracking System plugin (HPQcITSPlugin) for HP ALM/HPQuality Center EnterpriseIKAN Development has developed an IKANALM Defect tracking plugin forHP ALM/HPQuality Center Enterprise: the HPQcITSPlugin.Implementing this plugin will establish theautomated integration between the QA e HPQcITSPlugin uses the HP REST API tointeractwithHPALM/HPQualityCenterEnterprise. The plugin is a Java JAR file which isdeployed as part of the IKAN ALM web application.All required configuration parameters are storedin IKAN ALM and provided by the HPQcITSPlugin when they are required for request fulfillment.The HP Quality Center TestRunner (HPQcTestRunner)IKAN Development has developed a client toAs Maven 2 keeps all dependencies in local orautomatically trigger automated tests in HP ALM/remote repositories, a custom plugin has beenHP Quality Center Enterprise from within thedeveloped for Maven 2 which can start a javaIKAN ALM application: HPQcTestRunner.application from a JAR file (ikanExec-mavenplugin).HPQcTestRunner is a Pure Java COM client whichconnects to a registered Open Test ArchitectureCOM Server. Open Test Architecture representsan entry point to HP ALM/HP Quality CenterEnterprise and provides the capability to startautomated tests. Since OTA is a 32-bit COMobject, it must be deployed on a 32-bit Windowssystem. Although both IKAN ALM and HP ALM/HPQuality Center Enterprise support UNIX, theremust be at least one Windows installation to hostthe OTA COM object.During build or deployment procedures, IKANALM invokes various targets/goals defined inbuild and deployment scripts. All parameters aredefined in IKAN ALM and, if required, they arepassed to a scripting tool as arious sample build scripts to start automatedtests from within IKAN ALM. HPQcTestRunner is aJava application.Where Development, Testing and Operations meet5

BenefitsThe integration of HP ALM/HP Quality Center Enterprise with IKAN ALM provides the followingbenefits:Benefits for HP ALM/HP Quality Center Enterprise customers: Better control over build environments, predictable build results, repeatable builds,nightly/automated builds, predictable deployment results, automated deployment totest/production systems. Committed source code changes (potential bug fixes, new features) are automatically Functional test results will be launched after each build and automatically reported toreported to the HP ALM/HP Quality Center Enterprise defect tracking system.the HP ALM/HP Quality Center Enterprise testing module.Benefits for IKAN ALM customers: Requirements managementAutomated test case generation from requirementsTest scheduling and executionAccess to other testing products through HP ALM/HP Quality Center EnterpriseImplementation scenarioThe IKAN ALM Issue Tracking System plugin (HPQcITSPlugin) for HP ALM/HP Quality Center EnterpriseThe IKAN ALM Issue Tracking functionality provides the possibility to link Defects from an externaldefect tracking system to an IKAN ALM Level Request. Defects can be linked to a Level Request in thefollowing ways:12Via an automated search for handled Defects in the comments provided by the developerswhen committing or checking in sources into the VCR. This automated search is done ina separate phase during the handling of a Build Level Request, and is based on a regularexpression describing the Defect tracking number format. Currently this is only supportedfor a Subversion or CVS Version Control Repository.36Via manual addition of a Defect to a successful Level Request, using the GUI widgets onthe IKAN ALM Level Request Detailed Overview panel.Via the enumeration of solved Defects when delivering to Test/Production levelsenabling easy generation of Release Notes.Where Development, Testing and Operations meet

The scenario is as follows:1An IKAN ALM Defect is updated with the content of an HP ALM/HP Quality CenterEnterprise DefectThe HPQcITSPlugin provides a solution for automated updates of IKAN ALM Defects linked toHP ALM/HP Quality Center Defects on Build, Test and Production levels. (An HP ALM/HP QualityCenter Enterprise Defect can be opened from within IKAN ALM with a single click).2The IKAN ALM Defect is linked to a Defect stored in HP ALM/HP Quality Center EnterpriseThe HPQcITSPlugin provides a mechanism for updating Defects in HP ALM/HP Quality CenterEnterprise from within IKAN ALM.Where Development, Testing and Operations meet7

The HP Quality Center Issue Tracking System plugin (HPQcITSPlugin)HPQcTestRunner provides a mechanism for IKAN ALM to trigger automated tests created by QTP/UFTand stored in ALM/QCE. By adapting the IKAN ALM project build and/or deploy scripts, the automatedtests are triggered after every automated build or deploy. As a result, the number of faulty builds/deploys will be minimized.The following screenshots show the automated test set execution log in IKAN ALM and the resultslogged into HP ALM/HP Quality Center Enterprise.8Where Development, Testing and Operations meet

The automated tests in HP Quality Center can be triggered in different ways:1By Ant Test RunnerAnt Test Runner runs specific HP ALM/HP Quality Center Enterprise sets of tests or wholetest folders according to the configuration defined in the Ant XML script. Test results canbe ignored or they can stop a whole build.2By Maven 2 Test RunnerMaven 2 Test Runner runs specific HP ALM/HP Quality Center Enterprise sets of tests orwhole test folders according to the configuration defined in the Maven 2 POM file. Testresults can be ignored or they can stop a whole build.3By NAnt Test RunnerNAnt Test Runner runs specific HP ALM/HP Quality Center Enterprise sets of tests orwhole test folders according to the configuration defined in the NAnt XML script.Test results can be ignored or they can stop a whole build.Architectural components used for this solution HP ALMis a unified platform for accelerating and simplifying application delivery andempowering application teams – which include quality and development teams –to deliver better results for the business. HP ALM 11 provides actionable informationand workflows designed to accelerate delivery of secure, reliable, modern applications.Its key capabilities include cross-project planning and tracking, requirements definitionsand management with integration to business process models, complete traceabilityfrom requirements through developer tasks, testing and defects, and support formultiple development methodologies such as agile and waterfall. In addition, HP ALMshares a common foundation with HP Quality Center Enterprise and supports completequality planning and management, asset sharing, innovative manual testing with HPSprinter, and integrated automated testing. HP Quality Center EnterpriseHP Quality Center Enterprise software manages application quality across the entire application lifecycle. It provides requirements management, release and lifecycle management,test management, defect management, and reporting – all from a single platform. It alsoincludes a robust repository for your test cases and defects. To close the loop on yourapplication lifecycle, HP Quality Center Enterprise includes a full-featured requirementsmanagement system with a risk-based quality management module so that you can effectively gauge the risk of release.Where Development, Testing and Operations meet9