Remote Launch Integration Model w/Test Automation Tool

Friday, March 11, 2011
It appears that now.. w/Remote Launch(RL).. the only way to get result data from the automation tool (e.g. TestComplete) into SpiraTeam is to use SpiraTeam & RL as THE driver of the of the automation tool itself. 

The standard model is to have the Continuous Integration tool (e.g. Hudson) act as the driver of the automation tool.. and SpiraTeam consume the test results.  That work flow.. works.

Is there a way we can get our test results from the automation tool into SpiraTeam without using SpiraTeam & RL as the driver (of the automation tool)?

11 Replies
Friday, March 11, 2011
re: tomasino Friday, March 11, 2011
Michael Tomeo
It appears that now.. w/Remote Launch(RL).. the only way to get result data from the automation tool (e.g. TestComplete) into SpiraTeam is to use SpiraTeam & RL as THE driver of the of the automation tool itself. 

It depends on the automation tool. Unit testing tools are usually part of the build and as such our integration (e.g. JUnit, NUnit) works with SpiraTest being the passive receiver of the test results and the third party tool doing the launching.

For GUI testing tools such as QTP and TestComplete we have a different model where SpiraTest and RemoteLaunch do the launching so that you can more easily schedule and execute tests across different platforms and environments.

Specifically for TestComplete, the old plugin is still available (upon request) if you need it - the one that was launched by TestComplete itself.

Monday, March 14, 2011
re: inflectra.david Friday, March 11, 2011
Hey thanks. 

We have a plug file called "SpiraTestCompletePlugIn.pls" (dated May 25, 2009).  If there's a newer version then YES.. want/need to make a formal request for the plug.

I tried installing this SpiraTestCompletePlugIn.pls plug in TestComplete v8.2 and I get the following error:

"Cannot obtain information the plug-in(s) from the .pls file"

This worked in previous versions of TestComplete (v7) and SpiraTeam.. The  successful integration played a factor in purchasing both really want/need restoration of this functionality. 

Else, our automation results processing will occur completely outside of SpiraTeam.

Thanks again.

Tuesday, March 15, 2011
re: tomasino Monday, March 14, 2011

Hi Michael

There is a newer version of the TestComplete.pls file available that should work with TC8.x. I have posted it at

However that code is no longer being maintained so when TestComplete 9.x comes out it will no longer work with it. At that time you'll need to plan on switching over to RemoteLaunch. One option with RemoteLaunch would be to have your continuous build server actually fire RemoteLaunch...

Tuesday, March 15, 2011
re: inflectra.david Tuesday, March 15, 2011
That worked..we're back!
Thank you very much.

"have your continuous build server actually fire RemoteLaunch."
I knew you were gonna say that!  Just feels wrong..gonna have to meditate on that for a long while.

Thanks again for the plug update. 
It's much appreciated.

Wednesday, March 16, 2011
re: tomasino Tuesday, March 15, 2011
You are welcome.
Wednesday, March 16, 2011
re: inflectra.david Wednesday, March 16, 2011
Hello again,

Back with a follow on question.

For reporting purposes, we want/need to get results to percolate up through a "Test Set".  Right now we only see results percolated up from the "TestCases" to a "Test Run"..leaving any Test Set data out of the mix.  Looking to get the Test Set data into the Test Run Detailed Report.

Here's a sample mapping config.:
    <project id="000006" releaseId="000053">
        <test name="v8.2Check">
          <item name="ProjectTestItem2">001436</item>
          <item name="ProjectTestItem1">001438</item>
          <item name="ProjectTestItem3">001439</item>

Is there a "Test Set" attribute that can be configured in one of the elements?
Is there a configuration parameter in SpiraTeam that needs to be touched?

Thank You.
Friday, March 18, 2011
re: tomasino Wednesday, March 16, 2011

Hi Michael

The older integration with TestComplete does not support Test Sets, so unfortunately there is not a way of having the test results from TC update test set execution data in SpiraTest.

However that is possible with the newer RemoteLaunch way of integrating with TestComplete.

Monday, March 21, 2011
re: inflectra.david Friday, March 18, 2011
K', thanks.. 

Last question then.. 
With regard to the sample mapping config structure provided, are there any other data points (xml elements and/or attributes) currently support?

Thanks again.
Tuesday, March 22, 2011
re: tomasino Monday, March 21, 2011
No, those are the only ones supported (project, release, test case in Spira and project and test item in TestComplete).
Friday, December 16, 2011
re: inflectra.david Tuesday, March 15, 2011

I am interested in this integration model discussion too...

We are following a continuous delivery model, which requires our build (hudson/jenkins) to launch the automated tests, and react to the results (stop/continue/send alerts), while also feeding back the results to a central repo.

SpiraTeam/RemoteLaunch appears to satisfy most of the requirements, but I am wondering how the build server will react to the results of the test run.

Even getting it to wait for the test to complete appears difficult.

For instance, a simpllified example.

Currently, we have hudson/jenkins building to test, launching SoapUI tests, then releasing on successful completion.  Results are manually added to SpiraTeam.

Experiments with RemoteLaunch command line show it will schedule launches, including immediate launch, but it completes immediately and does not receive back any result (errorlevel).  The tests are then launched independently, and report results to SpiraTeam.

How can our build server launch tests (eg SoapUI project), then wait and receive back the result, in order to decide on the next task to perform, while the tests continue to report results to SpiraTeam?


Monday, December 19, 2011
re: cstott Thursday, December 15, 2011

Hi Charlie

RemoteLaunch was build primarily to be used to have SpiraTest/SpiraTeam launch the tests and have the results be returnd back to SpiraTeam. The command-line options were added to enable the system to be triggered outside of SpiraTeam as well.

We're going to be looking at the whole integration with CI tools such as Hudson next year once v3.2 is released. This new version of SpiraTeam (v3.2) has significant new features for integrating with CI tools and we will be re-evaluating RemoteLaunch as part of the process.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Friday, March 11, 2011
  • Last Reply: Wednesday, May 10, 2023
  • Replies: 11
  • Views: 11587