Unbinding Projects and Project Suites From Source Code Control (Legacy)

Applies to TestComplete 15.40, last modified on July 05, 2022
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.

After you have added your TestComplete project to a source control system, you can check in and check out project files, compare them, view file properties and accomplish other tasks by using items of the TestComplete File | Source Control menu, or items of the Source Control subitem of the Project Explorer’s context menu, or items of the Source Control toolbar (see Working With Source Code Control Systems). All these actions will be performed with the source control system, to which you added the project. That is, project item files must reside in the same source control database, in which the project holding this item is stored.

To Unbind a Project or Project Suite from a Source Control System
  • Right-click the project or project suite node in the Project Explorer panel and choose Source Control | Unbind From Source Control from the context menu.

-- or --

  • Select the project or project suite node in the Project Explorer panel and then choose File | Source Control | Unbind From Source Control from the main menu of TestComplete or click Unbind From Source Control on the Source Control toolbar (if the toolbar is hidden, right-click the main menu and select Source Control in the ensuing context menu to show the toolbar).

If a project was added to the source control system when you added the project suite, this project will also be unbound from the source control system when you unbind the project suite. If you added the project to the source control system separately from the project suite, the project will not be unbound from the source control as you unbind the project suite.

See Also

Legacy Integration With Source Control Systems - Common Tasks
Binding Test Projects to Source Control (Legacy)
Changing Source Control System or File Location in It (Legacy)
Integration With Source Control Systems via SCC API Providers (Legacy)

Highlight search results