VersionOne TestComplete Integration

Table of Contents

Description

The VersionOne TestComplete Integration (V1TestComplete) imports TestComplete test results into VersionOne, making the latest test results more visible across the organization. The results can be recorded at two different levels of granularity, project and test. The aggregate results for a suite of tests in TestComplete can be linked to a project in VersionOne, so that everyone can see the health of their project from a testing standpoint from within VersionOne. The results of an individual TestComplete acceptance test can be linked to a Test in VersionOne, so that development team members receive quick feedback on which tests are passing and failing.

Once V1TestComplete has been installed, VersionOne users update the reference field for test suites or tests with the path to the corresponding suite or test in TestComplete. A single VersionOne test suite can be assigned to one or more VersionOne projects. 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 individiual tests, each test in VersionOne should have its own test in TestComplete. V1TestComplete considers a test passing if all of the assertions for that test are passing. If a test fails on a story or defect that is already closed, V1TestComplete can be configured to create a defect in the current iteration, so the team is notified of the failing test.

System Requirements

VersionOne: 9.0 or above

Integration Server:

Operating System — Windows 2003, 2008
Framework—Microsoft .Net 2.0 SP1
AutomatedQA TestComplete Release 6.5.2 - 7.0.409.3

Downloads

The latest version of V1TestComplete is available at V1: Integration Downloads.

Installation

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

1. Determine Install Location

V1TestComplete can be installed on any server with network access to both your VersionOne and the TestComplete Test results. Exact placement should be determined by your internal software management requirements. The integation server must meet the System Requirements stated above.

2. Extract Files

Download V1TestComplete using the link above and extract it into a folder of your choice.

3 Configuration

Configure ServiceHost

The ServiceHost program (VersionOne.ServiceHost.exe) periodically checks a TestComplete project for updated test information. In order to operate this program needs to know what project to check, and how often to check for files. These parameters are specified in the TCReaderService element in VersionOne.ServiceHost.exe.config. You can edit this file with any text editor (i.e. Notepad). The following table describes these parameters

Table 1. TCReaderService Configuration Parameters

Parameter	Description
ProjectSuitConfig	Fully qualified path to TestComplete project file
RetryTimeout	Timeout between attempts to process test results while TestComplete is executing the tests
RetryAttempts	Number of times to attempt result process before skipping

Additionally, the integration needs to know how often to check the TestComplete project for updates. This time is controlled by the Interval element in the TCReaderServiceTimer element. The value is specified in milliseconds.

Table 2. TCReaderServiceTimer Configuration Parameters

Parameter	Description
Interval	The interval, in milliseconds, between events raised (via publishing the IntervalSync)
PublishClass	Contains the class and its' assembly that that the TimePublisherService will publish at every interval. For FIT integration using the FitServiceReader, it must be set as in the example below.

Note

When using the integrated authentication security setting, V1TestComplete will login 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.

Example 1.

<TCReaderService class="VersionOne.ServiceHost.TestServices.TestComplete.TCReaderService, VersionOne.ServiceHost.TestServices">
	<ProjectSuitConfig>C:\Program Files\Automated QA\TestComplete 6\Samples\Open Apps\OrdersDemo\C#\TCProject\Orders.pjs.tcLS</ProjectSuitConfig>
      <RetryTimeout>9000</RetryTimeout>
      <RetryAttempts>10</RetryAttempts>
</TCReaderService>
	<TCReaderServiceTimer class="VersionOne.ServiceHost.Core.Services.TimePublisherService, VersionOne.ServiceHost.Core">
	<Interval>10000</Interval>
	<PublishClass>VersionOne.ServiceHost.TestServices.TestComplete.TCReaderService+IntervalSync, VersionOne.ServiceHost.TestServices</PublishClass>
</TCReaderServiceTimer>

Configure VersionOne

Before V1TestComplete can update a test in VersionOne you must associate the VersionOne test with the TestComplete test. To configure this association, you need to edit the VersionOne Test artifact and enter the TestComplete test suite and test name in the Reference field.

Figure 1.
In order for the Test Run Trend reports to function properly, your TestComplete Test Suite needs to be associated with a VersionOne Project. To accomplish this you need to create a TestSuite in VersionOne, set the appropriate fields, and assigning this suite to a Project.

A VersionOne TestSuite is created from the Administration | Project | TestSuite menu.

Figure 2.

The Reference attribute on the VersionOne TestSuite must match a test suite in TestComplete.

Figure 3.

Finally, assign the TestSuite to the appropriate project.

Figure 4.

4. Start up

Open up the command prompt, navigate to your installation folder, and run the following command: VersionOne.ServiceHost.exe

Here is the expected output

Example 2.

C:\V1\TestComplete>VersionOne.ServiceHost.exe
Loaded VersionOne.ServiceHost.Logging.ConsoleLogService, VersionOne.ServiceHost.Core.
Loaded VersionOne.ServiceHost.Logging.FileLogService, VersionOne.ServiceHost.Core.
Loaded VersionOne.ServiceHost.Core.Services.TimePublisherService,VersionOne.ServiceHost.Core.
Loaded VersionOne.ServiceHost.TestServices.TestComplete.TCReaderService, VersionOne.ServiceHost.TestServices.
Loaded VersionOne.ServiceHost.Core.Services.TimePublisherService, VersionOne.ServiceHost.Core.
Loaded VersionOne.ServiceHost.TestServices.TestWriterService, VersionOne.ServiceHost.TestServices.
[Info] Initialized ConsoleLogService
[Info] Initializing FileLogService
[Info] Initialized FileLogService
[Info] Initializing ProfileFlushTimer
[Info] Initialized ProfileFlushTimer
[Info] Initializing TCReaderService
[Info] Initialized TCReaderService
[Info] Initializing TCReaderServiceTimer
[Info] Initialized TCReaderServiceTimer
[Info] Initializing TestWriterService
[Info] Initialized TestWriterService
[Startup]

5. Test the Service

To test the integration, execute a TestSuite in TestComplete.

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

Example 3.

C:\V1\TestComplete>VersionOne.ServiceHost.exe
Loaded VersionOne.ServiceHost.Logging.ConsoleLogService, VersionOne.ServiceHost.Core.
Loaded VersionOne.ServiceHost.Logging.FileLogService, VersionOne.ServiceHost.Core.
Loaded VersionOne.ServiceHost.Core.Services.TimePublisherService,VersionOne.ServiceHost.Core.
Loaded VersionOne.ServiceHost.TestServices.TestComplete.TCReaderService, VersionOne.ServiceHost.TestServices.
Loaded VersionOne.ServiceHost.Core.Services.TimePublisherService, VersionOne.ServiceHost.Core.
Loaded VersionOne.ServiceHost.TestServices.TestWriterService, VersionOne.ServiceHost.TestServices.
[Info] Initialized ConsoleLogService
[Info] Initializing FileLogService
[Info] Initialized FileLogService
[Info] Initializing ProfileFlushTimer
[Info] Initialized ProfileFlushTimer
[Info] Initializing TCReaderService
[Info] Initialized TCReaderService
[Info] Initializing TCReaderServiceTimer
[Info] Initialized TCReaderServiceTimer
[Info] Initializing TestWriterService
[Info] Initialized TestWriterService
[Startup]
[Info] Starting Processing File: C:\Program Files\Automated QA\TestComplete 6\Samples\Open Apps\OrdersDemo\C#\TCProject\C#Script\Log\5_19_2009_1_04 PM_45_362\RootLogData.dat
[Info] Found 2 testRuns and 1 suiteRuns.
[Info] Publising suiteRun: Orders.Orders_C#_C#Script - TestComplete Test Suite - 5/19/2009 1:04:58 PM - Orders.Orders_C#_C#Script - (1,1,0) 0 ms
[Info] Suite:
                TestRun.TestSuite = TestSuite:1743
                TestRun.Name = Orders.Orders_C#_C#Script
                TestRun.Description = TestComplete Test Suite
                TestRun.Date = 5/19/2009 1:04:58 PM
                TestRun.Passed = 1
                TestRun.Failed = 1
                TestRun.NotRun = 0
                TestRun.Elapsed = 0

[Info] Publising testRun: 5/19/2009 1:04:58 PM - Orders_C#_C#Script.ProjectTestItem2 - Failed - 0.0160008436068892 ms
[Info] Publising testRun: 5/19/2009 1:04:58 PM - Orders_C#_C#Script.ProjectTestItem1 - Passed - 13.6090025771409 ms
[Info] Finished Processing File: C:\Program Files\Automated QA\TestComplete 6\Samples\Open Apps\OrdersDemo\C#\TCProject\C#Script\Log\5_19_2009_1_04 PM_45_362\RootLogData.dat