Forum Discussion
You shouldn't use FindChild for Sys object because in this case TestComplete will search inside all running processes.
Better practice is to search objects inside the needed process. It will take less time.
If you don't want write browser name then use Sys.Browser().FindChild(<params>) object.
Maybe TestComplete 11 now tries to search from another end of the process list and it causes "slow" speed. :)
- mfoster7119 years agoRegular Contributor
While I agree that you should always try searching from the most sepcific object you can, unfornuately, that is not always possible.
I turned in a support ticket for this and they acknoledged the issue and turned it over to their developers. In the example I gave to Smartbear support, I have 3 lines of code that used Sys.Findchild and these 3 lines took less than a second to complete in TC10 and are taking over 2 minutes to complete in TC11. I repeated the test multiple times in the exact same environment and TC10 was always less than a second and TC11 was always over 2 minutes. This is not an issue with my code, it is an issue with TC11.
Edit: I was running my tests using IE 11, Firefox 37 and Chrome 45. All of them took over 2 minutes when running the test in TC11. I see many other threads where people are having slowdowns in Chrome and made it sound like this is a Chrome only issue but in my experience this is a global TC11 issue.
- mfoster7119 years agoRegular Contributor
This is a very frustrating situation. This break means we have had to hold off on upgrading all our PCs to use TC11. This always means we are unable to do any Google Chrome testing because you have to have TC11 to test Chrome 45.
- eykxas8 years agoFrequent Contributor
I have the same problem with TC12. My test duration with TC10 is about 1min now with TC12 it's about 30min !
Related Content
- 3 years agoAdim
Recent Discussions
- 44 minutes agoSubhraDas
- 20 hours agotramuntana