Supported Source Control Systems

Built-in integration is available for:

• CollabNet Subversion

• Git

• Mercurial

• Microsoft Team Foundation Version Control

TestComplete can also access any source control systems compatible with Microsoft Source Code Control API (SCC API). This approach is obsolete, but is left for backward compatibility. Source control systems supported using this approach include, but are not limited to:

• AllChange

• AllFusion Harvest Change Manager

• Code Co-op

• CollabNet Subversion 1.7.x – 1.8.x (the 32-bit version).

  Note:

  Working with Subversion via SCC API is not recommended, use the Subversion integration plugin instead. Existing Subversion SCC API users should migrate to the new Subversion integration as explained in Migrating From Legacy SCC API Providers.

• CM Synergy (Continuus CM)

• CS-RCS

• Concurrent Versions System (CVS), through the CVSProxy or Jalindi Igloo plugin

  Note:

  Access to TortoiseCVS via the Jalindi Igloo plugin is not supported.

• IBM VisualAge TeamConnection

• Merant PVCS Version Manager

• Microsoft Visual SourceSafe versions 6.0d and 2005

• Microsoft Team Foundation Version Control via the 32-bit version of MSSCCI Provider (can be downloaded from Microsoft Download Center).

  Note:

  Working with TFVC via the SCC API is not recommended, use the TFVC integration plugin instead. Existing users should migrate to the new TFVC integration as explained in Migrating From Legacy SCC API Providers.

• MKS Source Integrity

• Perforce P4 Version Control System

• Rational ClearCase 2003.06 and later

• Seapine Surround SCM

• SourceGear SourceOffSite

• SourceGear Vault 7.1 or later

• Starbase Versions (StarTeam)

• Team Coherence