We know exactly why the test is failing. Test Execute is not frozen.
An error occurs in our app that causes TestExecute to wait, assuming the error will be dismissed. When the error is not dismissed, TestExecute continues waiting on the error to go away.
We're fine with that, that isn't our issue. Our issue is that once TestExecute has been waiting for more than the pre-configured test timeout, the TestComplete Jenkins plugin will terminate TestExecute without proper error output being delivered.
In fact, the plugin reports that the test 'failed to start' which isn't true.
So at this point ,we aren't told what happened during the test run. We happen to know exaclty what hapened in this case, but this is an error in your plugin. We should be shown what happened, not have to investigate it for ourselves after the test run.
Bump
