Forum Discussion
It still fails with your code as well...
I tried changing the 'Method invoke timeout, ms:' from the default of 3000 up to 30000.
That was a good idea, I didnt know about that timeout setting, but unfortunately I has not corrected the issue..
I looked at the log for the steps this time rather than the report.
I noticed this:
"TestComplete (TestExecute) was stopped, because the specified timeout for the run elapsed. The following error occurred: The execution time specified in the command line has expired."
Is it possible that because I am using a trial license of TestExecute ( I am working on a proof of concept), that there is a timeout passed via the command line??
Or maybe it could be something that is getting passed from QAComplete... hmmm...
jmcwhinney wrote:Is it possible that ................that there is a timeout passed via the command line??
Or maybe it could be something that is getting passed from QAComplete... hmmm...
That seems to have been the issue.... I had the default timeout of 30 set in QAcomplete where I was calling the test..
Cheers,
- James
- Ryan_Moran10 years agoValued Contributor
It's always the simplest of solutions that are the most difficult to find :manlol:.
Glad it's solved anyhow.
Related Content
- 4 years ago
Recent Discussions
- 10 hours ago
- 7 days ago
- 10 days ago