Forum Discussion

KLabrie's avatar
KLabrie
Occasional Contributor
8 years ago

Object invoked disconnect from client at website deployment

Hi,   I need to run smoke test at the deployment of our website. The test works, except at the deployment. I always get an error native.   Error: The object invoked has disconnected from its clie...
  • KLabrie's avatar
    KLabrie
    8 years ago

    I fix my problem,

     

    I was getting a problem cause the time i was getting the document object and the time i was doing a query selector. The page was refreshing (due to the first load) and then my object got disconnected when trying to do the querySelector.

     

    Basicly i did :

     

    try
{
   fromElement = getCurrentPage().contentDocument;
   elemFound = fromElement.querySelector(cssSelector);
}
catch (ex)
{
    fromElement = null;
    elemFound = null;
}

    So if the problem occur i just continue my loop and return null if I don't get what i want ater the timeout (for my case, it's doing what i want). 

tristaanogre's avatar
tristaanogre
Esteemed Contributor

Here's my thinking... and this is just a guess, mind you.

Since it is running just fine after the deployment is done, my guess is that there is some code processing happening during the deployment that is causing pages to refresh or objects on those pages to refresh.  So, handles to a particular page might be destroyed or reset during that processing.  Looking at the "getCurrentPage" method, that is my candidate for the problem.

 

Do you have a particular line of code that is generating that error?  If you double click on the error in the TestComplete log, what line does it take you to?  That might help narrow down the issue a bit more.

KLabrie's avatar
KLabrie
Occasional Contributor
8 years ago

When the error occurs, double clicking on the log take me to the closest catch.

 

And Your idea of the website doing a refresh, that what I think too, but wanted an approval of this idea.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago

    There's no "catch" statement in the code you posted... so, I'm assuming the catch is being picked up somewhere else?

    Might not be a bad idea, for debugging purposes (if not simply to make some "good" code out of it) to add try/catch/finally logic to these routines to see if we can find where the problem is happening.  If you're running JavaScript, you can even, in your catch, write the stack to the log like

     

    try {
//do stuff
}
catch (e) {
    Log.Warning('Something dumb happened: ' +e.message, e.stack);
}
finally {
//clean up on row 12....
}
    • KLabrie's avatar
      KLabrie
      Occasional Contributor
      8 years ago

      Yeah, I have have code like :

      try
{
   test();
}
catch(ex)
{
   Log.Error("", ex.stack);
}

      And the line that cause the error in the call stack is the line with the querySelector()

      • baxatob's avatar
        baxatob
        Community Hero
        8 years ago

        Hi,

         

        Please describe your deployment procedure step-by-step.