Forum Discussion

jmcwhinney's avatar
jmcwhinney
Contributor
11 years ago
Solved

'The execution timeout has expired' within 1 second during a .WaitProperty("Exists",true,5000). How?

My script runs fine on my development PC, but when I schedule it using TestExecute on a different PC, it seems to fail randomly.   Most recently, it has failed within 1 second of the test item. Lo...
  • jmcwhinney's avatar
    jmcwhinney
    11 years ago
    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_Moran's avatar
Ryan_Moran
Valued Contributor
11 years ago

Do you get the suddenly random timeout with the code I provided?
Your code would have decreased the timeout for each object as it iterated the array so I could see that failing "seemingly at random".

 

If it still fails with my supplied code:

You can adjust the Method Invoke Timeout under your project settings > open applications to see if that helps.

jmcwhinney's avatar
jmcwhinney
Contributor
11 years ago

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...

 

 

  • Ryan_Moran's avatar
    Ryan_Moran
    Valued Contributor
    11 years ago

    Check to make sure you don't have a timeout specified under View>Organize Tests>[Timeout,min] column of your test item.

  • jmcwhinney's avatar
    jmcwhinney
    Contributor
    11 years ago
    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_Moran's avatar
    Ryan_Moran
    Valued Contributor
    11 years ago

    It's always the simplest of solutions that are the most difficult to find :manlol:.

    Glad it's solved anyhow.