Typically, to organize teamwork, developers use various source code control systems.
You can use TestComplete as a client for your source control, that is, you can work with your source control system directly from the TestComplete IDE. For the list of source control systems TestComplete supports, see Integration With Source Control Systems.
Bind your test projects to source control to organize teamwork:
Create a new project or open an existing project in TestComplete.
Bind a project suite (or a single project) to a source control system.
As an alternative, you can add your project or project suite to the source control repository manually.
Note: You do not need to add all project files to source control. For example, we do not recommend adding log items to source control.
To learn what files you should add to source control, see List of Files Added to Source Code Control
Update the local version of the project with changes from your source control repository.
If you connect to your source control via SCC API Provider, check out the needed files.
Modify the project (or its elements) as you need. Save the changes.
Commit your changes. If you use Git or Mercurial, send your changes to your remote repository.
If you connect to your source control via SCC API Provider, check in the changed files.
If you no longer need to store your project in the source control system, unbind it from the repository.
You can also open test projects and project suites that are stored in a source control system directly from the TestComplete user interface.
For more information on TestComplete integration with source control systems, see the topics of the Integration With Source Control Systems section.
Using Source Control Systems for Teamwork - Specifics
Using Source Control Systems for Teamwork - Overview
Using Source Control Systems for Teamwork
Integration With Source Control Systems via SCC API Providers (Legacy)