Forum Discussion

Ryu's avatar
Ryu
Contributor
4 years ago

ReadyAPI timeout causing failure within TestComplete test run.

I have several ReadyAPI calls as part of my project suite and for some reason many of them fail during a test run because of exceeding the read timeout.  I can run each of these ReadyAPI calls indivi...
Ryu's avatar
Ryu
Contributor
4 years ago

I'm not sure what good a screenshot would do for a ReadyAPI call?  This is literally happening with every ReadyAPI call I make across several different scripts.  Here are some examples:

 

 

 

Marsha_R's avatar
Marsha_R
Icon for Champion Level 3 rankChampion Level 3
4 years ago

You said that it runs if you do it manually and doesn't when you run within TestComplete, therefore I'm looking for a problem in the code or the code right around it in TestComplete.  

 

 

  • Marsha_R's avatar
    Marsha_R
    Icon for Champion Level 3 rankChampion Level 3
    4 years ago

    Did you try my last suggestion?  What happened when you did that?

  • Ryu's avatar
    Ryu
    Contributor
    4 years ago

    Marsha_R Gotcha.  Maybe I need some kind of delay between commands?  This seems to be a new problem with ReadyAPI 3.8 (or maybe even the latest TC update) as it wasn't happening until just a few weeks ago.

  • Marsha_R's avatar
    Marsha_R
    Icon for Champion Level 3 rankChampion Level 3
    4 years ago

    Do you have something that you can check after that Delay and then after that setup line to make sure that everything actually started up and was setup the way you expect before you start with the Execute?  TC doesn't slow down any in between any of those things, so even though you had a delay, the service may not be ready and TC is going on with the SetupAVL line (which could be not ready on it's own) and then going on to Execute lines immediately. 

     

     

     

     

  • Ryu's avatar
    Ryu
    Contributor
    4 years ago

    Marsha_R I'm not sure what else to do here.  The first ReadyAPI call in any script still "fails" stating timeout for the reason.

  • Ryu's avatar
    Ryu
    Contributor
    4 years ago

    There isn't anything else to check, that I know of.  I put in delays, but it still sometimes marks the ReadyAPI call as failed even though it actually went through.