Description

The VersionOne Quick Test Professional Integration (V1QuickTestPro) imports the results of tests defined HP's Quick Test Professional (QTP) into VersionOne. The results of an individual QTP test can be linked to a Test Artifact in VersionOne, so that development, and you organization, will receive quick feedback on which tests are passing and failing.

Once this integration is installed, VersionOne users update the Reference field on a VersionOne Test with the test names defined in QTP. The Test Run Trend report shows the aggregated test results for the test suite which was assigned to the project at the time of the test run. For individual tests, each test in VersionOne should have its own test defined in QTP. If a test fails on a story or defect that is already closed, V1QuickTestPro can be configured to create a defect in the current iteration, so the team is notified of the failing test.

The following sequence diagram illustrates how V1QuickTestPro interacts with QTP and VersionOne.

System Requirements

• VersionOne: 7.1 or above, including Team Edition
• Integration Server:
  • Operating System — Windows 2003, 2008
  • Framework—Microsoft .Net 2.0 SP1
  • HP Quick Test Pro—Release 9.2 — 10.0

Download

The latest version of V1QuickTestPro is available from the VersionOne Community site

Installation

These installation instructions assume that QTP is already installed, configured, and working properly.

1. Determine Install Location
   V1QuickTestPro can be installed on any server with network access to both VersionOne and your QTP Test results. Exact placement should be determined by your internal software management requirements. The integration server must meet the System Requirements stated above.
   
   
2. Extract Files
   Download V1QuickTestPro using the link above and extract it into a folder of your choice.
   
   
3. Configure
   1. Configure VersionOne
   2. Configure The Integration
      
      
4. Start integration
   Open up the command prompt, navigate to your installation folder, and run the following command:

   VersionOne.ServiceExecutor.exe

   If you have configured your system properly, you should see the following output when there are no results to publish into VersionOne

   C:\V1MercuryQTP>VersionOne.ServiceExecutor.exe
   Loaded VersionOne.ServiceHost.Logging.ConsoleLogService, VersionOne.ServiceHost.Core.
   Loaded VersionOne.ServiceHost.Logging.FileLogService, VersionOne.ServiceHost.Core.
   Loaded VersionOne.ServiceHost.TestServices.Mercury.QTPReaderService, VersionOne.ServiceHost.TestServices.
   Loaded VersionOne.ServiceHost.TestServices.TestWriterService, VersionOne.ServiceHost.TestServices.
   [Info] Initialized ConsoleLogService
   [Info] Initializing FileLogService
   [Info] Initialized FileLogService
   [Info] Initializing QTPReaderService1
   [Info] Initialized QTPReaderService1
   [Info] Initializing TestWriterService
   [Info] Initialized TestWriterService
   [Startup]
   [Shutdown]
   
   C:\V1MercuryQTP>
   

   
   

5. Test the integration
   Before testing you must execute at least one test. Once this is complete, open up the command prompt, navigate to your installation folder, and run the following command:

   VersionOne.ServiceExecutor.exe

   When V1QuickTestPro and VersionOne are configured correctly you should see data being published into VersionOne.

   C:\V1MercuryQTP>VersionOne.ServiceExecutor.exe
   Loaded VersionOne.ServiceHost.Logging.ConsoleLogService, VersionOne.ServiceHost.Core.
   Loaded VersionOne.ServiceHost.Logging.FileLogService, VersionOne.ServiceHost.Core.
   Loaded VersionOne.ServiceHost.TestServices.Mercury.QTPReaderService, VersionOne.ServiceHost.TestServices.
   Loaded VersionOne.ServiceHost.TestServices.TestWriterService, VersionOne.ServiceHost.TestServices.
   [Info] Initialized ConsoleLogService
   [Info] Initializing FileLogService
   [Info] Initialized FileLogService
   [Info] Initializing QTPReaderService1
   [Info] Initialized QTPReaderService1
   [Info] Initializing TestWriterService
   [Info] Initialized TestWriterService
   [Startup]
   [Info] Updating status of Acceptance Test "Test:1366:1598".
   [Info] Suite:
                   TestRun.Date = 11/20/2007 9:17:20 AM
                   TestRun.Failed = 1
                   TestRun.Elapsed = 0
                   TestRun.Description = Release10TestSuite on 11/20/2007 9:17:20 AM
                   TestRun.Passed = 2
                   TestRun.NotRun = 0
                   TestRun.Name = Release10TestSuite
                   TestRun.TestSuite = TestSuite:1771
   
   [Shutdown]
   
   C:\V1MercuryQTP>
   

6. Automate the process
   To automate the publishing of results after each test run is accomplished
   1. Create a QTP test script that calls VersionOne.ServiceExecutor.exe
      
   2. Add this script to the end of your QTP batch process.
      

Configuration

Configure VersionOne

If you are using Team Edition, you need to manually create the Test Suite. Instructions for doing this are available on the VersionOne Community Site.

1. Add a TestSuite in VersionOne
   1. A VersionOne TestSuite is created from the Administration | Project | TestSuite menu.
      
   2. The Reference attribute on the VersionOne TestSuite defined the association to the QTP Test.
      
2. Assign the VersionOne TestSute to a Project
   Once the TestSuite is created, it must be assigned to a Project. To accomplish this, edit the VersionOne Project details.
   
3. Set the Reference Field on Test that are automated using QTP
   Before V1QuickTestPro can update a VersionOne Test you must associate the VersionOne Test with a QTP test. To configure this association, you need to edit a VersionOne Test and enter the QTP Test Name in the VersonOne Reference field.
   

Configure the Integration

To configure V1QuickTestPro you need to run the ServiceHost configuration tool

ServiceHostConfigTool.exe

The following section describes how to configure your QTP integration using the use the configuration tool

1. Specify your VersionOne connection details on the General
   
   The following table describes the fields on this tab

   Field	Description
   Server URL	This is the URL to your VersionOne server
   Username	VersionOne user that will create defects
   Password	Password for the specified user
   Use Windows Integrated Authentication	Check this box if you VersionOne server is configured to use Windows Integrated Authentication

   When using the integrated authentication, V1QuickTestPro will authenticate to VersionOne using the Windows domain user under which the executable is running if both the username and password parameters are blank. If the username and password is entered, you must specify the windows domain account in the form "User@FullyQualifiedDomainName". If you are unsure what the fully qualified domain name is, see the Domain name shown on the 'Computer Name' tab in the My Computer...Properties dialog.

   If there's a proxy between this machine and the VersionOne instance, you'll also need to configure the following settings:

   Field	Description
   Use Proxy For Connection	Determines if the integration tries to connect through a Proxy
   Proxy URL	This is the URL to your Proxy Server
   Proxy Username	The username that will get you past this proxy
   Proxy Password	The password for the Proxy Username
   Proxy Domain	Name of Proxy Domain

2. Once the VersionOne parameters are entered, press Verify button to continue.
3. Specify how to update Test in VersionOne on the Tests tab.
   
   The following table describes the fields on this tab

   Field	Description
   Disabled	Check this box to disable ChangeSet creation in VersionOne.
   Reference Field Name	VersionOne Field name to search for QTP test identifier. It's recommended that you use the Reference field; however if you are already using this field for another purpose, you may choose another text field, including custom fields.
   Test Passed Status	Value to set when a QTP test passes
   Test Failed Status	Value to set when a QTP test fails
   Change Comment	Comment to use when setting values on VersionOne tests
   Description Suffix	If you are creating Defects, this text will appear in the description field
   Create Defect	Indicates whether V1QuickTestPro should create VersionOne Defects when a QTP test fails for closed tests in VersionOne. Valid values are: * All: The integration will create a VersionOne Defect for any closed test in the project when the QTP test fails * Current Iteration: The integration will only create VersionOne Defects for closed tests within the current iteration when the QTP test fails * None: The integration never create VersionOne Defects

4. Specify your QTP details on the Quick Test Pro tab.
   
   The following table describes the fields on this tab

   Field	Description
   Disabled	Check this box if you want to disable polling QTP for Test Results.
   Watch	The directory to poll for QTP test results files.
   Filter	The file filter to use when polling for QTP test results files; it may contain any valid search pattern (i.e. *.xml)
   Suite Name	The VersionOne Test Suite Name

5. Save your changes and exit the program

Technical Details

VersionOne.ServiceHost.exe.config

VersionOne.ServiceHost.exe.config is the file that controls the behavior of VersionOne.ServiceHost.exe. Values in this file are set by the configuration tool (ServiceHostConfigTool.exe). This section is provided for informational use only. Users are discouraged from editing this file directly.

The QTPReaderService watches for new result files, interprets QTP test results, and publishes the results to the TestWriterService. The following table describes the elements nested under TestWriterService.

The TestWriterService element controls how Tests are updated in VersionOne. The following table describes the elements nested under TestWriterService.