Last week, the name mapping operation, adding objects to the name mapping has become painfully slow. Has anyone seen this before? I can't think of anything that has changed. The app is the same. TC has not changed...
Solved! Go to Solution.
Apparently, they are aware of git issues now. Reply to my case
Our R&D team investigated the issue, and it seems that the Git integration causes the issue.
When new files are added during the recording, there is the setting that will automatically add them to the repository. So, let's disable that option and check if this improves the situation. To do that, go to "Tools | Options | Source Control | Bind new items to SCC automatically." Then, disable the "Bind new items to SCC automatically" option and try running TestComplete again.
Turning this option off solved the slow name mapping. I am unclear what features I am losing. If I don't use the source control ui through Test Complete, I am guessing not much.
Couple of things to check.
1) How exensively are you using "Extended Find" in your mapping? Each time in a hierarchy extended find is used, that's an additional "search" that is being done by the engine. This is not to say DON'T use the feature, just be aware that using it a lot may cause performance issues.
2) Are you using GIT as your source control? There have been several reports here on the forums that GIT, when activated as a source control, can slow down editing of NameMapping and other such things.
Hey, @TanyaYatskovska .... there have been NUMEROUS reports here on the community that activating the GIT source control plugin in TC 12.60 is causing rather serious performance issues. Do you know if there is anything that SmartBear staff know about that need to be done in order to make sure that this problem doesn't occur?
I am seeing info in docs about not using source control. Is there a way to disable source control entirely from within TestCompelete? I never use it. I use external tools. Thanks
If you go to Tools | Options | Source Control, if you don't have the GIT option enabled, then you're not using Source Control through TC...
...however, it could be that the GIT command line is still processing file changes that are done in TestComplete. This seems to be an issue with GIT and the fact that TC does a lot of file processing when doing NameMapping and executing test.... I'll wait and see what SmartBear says.
I've consulted with our TestComplete Support Team - they aren't aware of any GIT performance issue in TestComplete 12.6. If it's possible, I would suggest that you check if you see the same issues in TestComplete 14 (the latest product version).
Otherwise, please submit a support ticket so that our Customer Care Team could investigate this behavior. You can submit a support ticket here:
Thanks for checking this. Could you please resend this video along with the description of the issue to our Support Team? They will investigate this behavior. You can contact them here:
Thanks in advance.