I've had this happen pretty recently in my own projects. Usually, it comes down to a couple of things:
1) My NameMapping is insufficiently detailed to find an object, especially if I'm using the Extended Find feature. If I don't have enough parent objects in my tree, it takes a long time to find the specific object I want and TestComplete pretty much times out
2) If I'm in the middle of a Page.Wait call and I attempt to stop or halt the test, I get the same hang. But, again, this usually ends up happening because something else hung first.
Since you know that the problem is that an object is not found that is expected, that's your resolution.
For assistance, please post screenshots of your logs showing the errors around the unexpected object and the additional information panel for each error. Specifically, look out for warnings about "ambiguous recognition" or "object took too long" or things like that.
ok, but the problem is as I am ending the Test Execute task everytime, it doesn't post any log too.
Not having a log is to be expected in that case. If TestExecute doesn't finish on its own, then you probably won't get a log.
Hi,
> it doesn't post any log too
a) Have you included /SilentMode parameter into command line to prevent TestExecute from displaying error dialogs?
b) Try to check if the silent.log file exists and if it contains something relevant: https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/command-line.html (/SilentMode paragraph).
I looked at and i didn't see silent.log file anywhere in the project folder.
I will still look into to see any clues but this Isssue didn't happen in Text Execute or TestComplete verson 10 at all.
The scripts are suppose to run every 1/2 hour . Looks like it hanged today at 6:00 am and the scripts didn't execute since then.
This needs to be fixed.
1.Should I remove extended find at all levels of name mapping?
2. Also when ever I try to edit name mapping of an action , now it asks to open the following url in Browser (Firefox) which I didn't see before. Is this b'se I added Environment Manager in Project Suite.
Is this delaying in finding things? I don't see an option to delete this element.
Please suggest.
Considering that, based upon a previous thread, this is the first time, really, you're running theses tests on the VM as scheduled tasks, I'm not entirely sure that we can point to the version of TestExecute/TestComplete.
As noted above, you're going to have to spend some time debugging your tests to find out where the hang point is. You might need to sit and watch it run to see if you can figure out where it's happening and then do some examination of your tests to see what's going on. Again, the my main suspect in this is some inability to find an object that is resulting in a long wait time in object recognition.
Is there any way you can run your tests in segments? You know.. enable tests 1-3 and run it. If it runs, add tests 4-6 to the run, and so on, until you get it to hang. That should then target where the problem is and you can work on debugging.
Question: Is this a web application you're testing or a desktop application? If it's a web application and you notice TestExecute is hanging, have you checked to see, via Windows Task Manager, if there is an instance of your web browser present in memory that is, itself, somehow hung? If so, try killing that first before you kill TestExecute and then wait a bit and see if TestExecute exits on its own. If it does, it should write out a log and you should then be able to see where the fail point is.
