Forum Discussion

exdunepilot's avatar
exdunepilot
Contributor
9 years ago

Restarting AUT Within Code Leads to Very Slow or non-Existent Object Identification

As part of our test sequence, we restart the AUT within code using TestedApps.  The problem occurs as object identification of the restarted AUT becomes so slow its not usable (if its able to ID at all).  Also, at times, but not always we see an RPC Server unavailable error.  I've tried an explicit .Refresh() on the object tree right after restart but that does not help.  Any tricks to getting this to work with TestComplete 12.31 and JavaFX as our AUT technology? 

1 Reply

  • baxatob's avatar
    baxatob
    Community Hero

    Sounds like after restart your application has changed its identification properties, which used in NameMapping.