RemoteLaunch/SoapUI testrunner freezing

Thursday, December 15, 2011
When invoking SoapUI testrunner from RemoteLaunch a cmd.exe window is opened on the automation host, which remains blank, and never completes or closes by itself.

While the cmd window is open, SpiraTeam does not recognise the test run.

If the window is closed manually, SpiraTeam will be updated and report the results of the test run.

As the whole point is to automate testing, this manual intervention is not viable.

Is there a fix/workaround/setting, please?

3 Replies
Thursday, December 15, 2011
re: cstott Thursday, December 15, 2011
The plugin simply calls the command-line and waits for it to exit. When you run the tests manually through the command line (not through remote launch) does it automatically return control back to the command-line? If you run the script from the Windows > Start > Run button, does the command window automatically close
Friday, December 16, 2011
re: inflectra.david Thursday, December 15, 2011
Thanks for the reply.
Further investigation shows that the tests do eventually complete and return results to SpiraTeam. 

Scheduled runs appeared to run much slower than from the command line, but it seems that our host automation tool is the problem in this situation, taking it's default values from different places depending on how the tool is launched.

Kind Regards,
Monday, December 19, 2011
re: cstott Thursday, December 15, 2011
OK, glad that cleared things up.

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: Thursday, December 15, 2011
  • Last Reply: Monday, December 19, 2011
  • Replies: 3
  • Views: 6960