RemoteLaunch/SoapUI testrunner freezing

Thursday, December 15, 2011 5:06:19 AM
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?

Charlie
3 Replies
Thursday, December 15, 2011 9:32:40 PM
Avatar
re: cstott on Thursday, December 15, 2011 5:06:19 AM
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 12:37:44 AM
Avatar
re: inflectra.adam on Thursday, December 15, 2011
Hi,
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,
Charlie
Monday, December 19, 2011 3:48:50 PM
Avatar
re: cstott on Thursday, December 15, 2011
OK, glad that cleared things up.
Statistics
  • Started: Thursday, December 15, 2011 5:06:19 AM
  • Last Reply: Monday, December 19, 2011 3:48:50 PM
  • Replies: 3
  • Views: 4471