Forum Discussion
The problem you have is probably TC trying to find an object and due to the big amount of objects available in your app, the low amount of resources in your machine, or even your application doing something in the background, it hangs and it will stay like that until the internal "search" process of test complete finishes.
If your app is web based, I would suggest you not use the FindObject method and instead use the QuerySelector.
Another approach is to get the parent object of the object your are trying to find, and then use the FindObject from the parent object, thus reducing the amount of objects TC has to search.
Forget about configuring timeouts or that kind of stuff, TestComplete just ignores them all until it finishes doing what it is doing, which is kinda bad but that's how I found out it works.
Related Content
- 6 years ago
Recent Discussions
- 10 hours ago