Forum Discussion
Thank you for your response. I’d like to provide some additional context based on my workflow.
Previously, I used TestComplete’s built-in Git integration (through source control integration), and when I added a new script to the project, the Script.tcScript file was updated automatically. I did not need to manually press “Save All Changes” — the change was immediately visible in Git, and everything worked as expected.
Now that I’ve switched to using an external Git client (Fork), the behavior is different. When I add a new script file, I can see the file is created and marked with a “+” icon in TestComplete, meaning it’s new and tracked. However, unless I manually save the entire project, the Script.tcScript file does not get updated, so Git doesn’t detect any change in the project structure.
As a result, even though the new script exists and is versioned in Git, the Script.tcScript does not include it, and collaborators won’t see the script in the project unless I remember to save all changes manually.
David
I use Team Foundation Version Control Plugin, with Microsoft Visual Studio Team Explorer 2019. I no longer use the menu items that appear in Source Control in TestComplete, mainly because the TFS plugin is clunky and outdated.
I perform all my check-in/out etc via MS Visual Studio Team Explorer, as the user interface and functionality is a lot better. The TFS plugin in TestComplete, is only used for visual representation i.e. to see what's added/removed/updated etc. in Project Workspace -> Project Explorer.
I've ensured all testers follow this process, and we haven't have any issues since. Providing they "Save All Changes"!
I'm not sure how up-to-date the Git Plugin is, but find something that best works for you and others.