Forum Discussion
hlalumiere
13 years agoRegular Contributor
We have started migrating a very huge project (around 500 parent test items with about 10 children each on average) from TC8.2 to TC9, what I see is actually INCREASED performance in most case, however sometimes TC seems to "hang" doing nothing at all for 30-45 seconds, and then starts over again. It seems to be linked to the .FindAllChildren method, .FindChild method, and some others. Once in a while it won't find the object right away, and will go through whatever depth was selected, go all the way down, and finally return the correct window (which was sitting at the top of the hierarchy).
TC9 also seems very unstable at the moment. It routinely closes on us without warning, sometimes gets "stuck" after stopping a test execution, leaving us with no other choice than killing the process, becomes very slow after some hours of work, and consumes an increasing amount of memory over time. This to me points to a memory leak somewhere. Fresh after a reboot, it is much faster than TC8.2, but this quickly degrades after multiple runs.
We also encounter various errors in our tested application, all linked to TcVbHook.dll in the resulting stack trace, most common being runtime error 91. Our application is about 50/50 VB6 and VB.Net, with some C#.
I am not too worried about it for now, as we only have about 10% of the project converted to TC9, and this is the first release of the 9.0 branch, but I sure hope those issues are resolved by the time we are ready to deploy it to our test pool. We use TC to test and resolve the application's issue, not to create new ones.
Hugo Lalumière
Dynacom Technologies Inc.
TC9 also seems very unstable at the moment. It routinely closes on us without warning, sometimes gets "stuck" after stopping a test execution, leaving us with no other choice than killing the process, becomes very slow after some hours of work, and consumes an increasing amount of memory over time. This to me points to a memory leak somewhere. Fresh after a reboot, it is much faster than TC8.2, but this quickly degrades after multiple runs.
We also encounter various errors in our tested application, all linked to TcVbHook.dll in the resulting stack trace, most common being runtime error 91. Our application is about 50/50 VB6 and VB.Net, with some C#.
I am not too worried about it for now, as we only have about 10% of the project converted to TC9, and this is the first release of the 9.0 branch, but I sure hope those issues are resolved by the time we are ready to deploy it to our test pool. We use TC to test and resolve the application's issue, not to create new ones.
Hugo Lalumière
Dynacom Technologies Inc.
Related Content
- 3 years ago
Recent Discussions
- 2 days ago