Skip Navigation LinksHome Page > Forums > RemoteLaunch Forums > RemoteLaunch Issues & Que... > Remote Launch Integration...
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.
There is a newer version of the TestComplete.pls file available that should work with TC8.x. I have posted it at www.inflectra.com/Downloads/TestComplete8PlugIn.zip
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...
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.
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.