This topic describes functionality of the SCC API Providers plugin, which is obsolete and is left for backward compatibility only. To learn about supported source control integrations, see Integration With Source Control Systems. |
TestComplete source control services let you interact with source control systems directly from TestComplete. This feature helps you work with your projects bound to a source control system as you can check out files, modify them and put the changes to the source control system directly from the TestComplete IDE. For more information on how to perform basic operations using TestComplete support for source control systems, see Integration With Source Control Systems via SCC API Providers (Legacy).
Along with other operations, testers typically branch some files to have different tests for different product versions. Most source control systems provide users with special features for file branching. So, to branch a file bound to a source control system, use the native client of this source control system. For more information on how to do this, refer to your source control system’s documentation.
TestComplete does not provide features for file branching, so if you need to branch a file, the native client of the source control system must be installed on your computer. |
Also, after branching a file, you may need to flush the changes you have made to the default branch. In such cases, you will have to merge the file from the new branch and the same file from the default branch. There are several approaches used for file merging. For instance, you can use TestComplete or the native client of your source control system. For more information on merging files bound to a source control system, see Merging Files (Legacy).
See Also
Integration With Source Control Systems via SCC API Providers (Legacy)
Merging Files (Legacy)
Integration With Source Control Systems via SCC API Providers (Legacy)
List of Files Added to Source Code Control