TestComplete integrates into source code control systems, so you can check in and check out project files, view their properties, get the latest versions and perform other actions directly in the TestComplete environment.
TestComplete projects and project suites consist of a number of files that holds settings related to the project suite, projects, project items and their elements (see Project and Project Suite Files), so it is possible to perform the mentioned actions over project suite and project files as well as project item files and their child elements.
Below is a full list of project suite, project and project item files added to the source code control:
Project suite and project files:
CBT.data - Contains data on CrossBrowserTesting environments and tests to be run in those environments.
|Note:||The file does not store the CrossBrowserTesting account information that TestComplete uses to connect to the CrossBrowserTesting service.
Currently, TestComplete does not show status icons near the CrossBrowserTesting project suite item even if the item is bound to a source control system.
Events project item files:
Image Repository files:
Keyword Testing project item files:
Low-Level Procedures Collection project item files:
Manual Tests project item files:
The manual testing functionality is deprecated. Do not use it to create new tests. It will be removed from the product in one of the future releases.
Name Mapping project item files:
NameMapping.tcNM - Contains data of the Name Mapping project item.
Images.NMimg - If your Name Mapping repository is configured to store images of mapped objects, the file contains references the images.
Network Suite project item files:
Object-Driven Testing project item files:
The object-driven testing functionality is deprecated and is supported for backward compatibility only. Do not use it to create new tests. It will be removed in a future TestComplete release. As an alternative to the ODT functionality, you can create custom classes in your scripts. For more information, see Alternatives to the ODT functionality.
ReadyAPI or SoapUI project item files:
Scenarios project item files:
Scenarios.tcTestCases - Contains settings of the Scenarios project item and a list of BDD feature files in your project.
.feature - Feature files included in your project.
Script project item files:
Script.tcScript - Contains data of the Script project item.
.sj - A JScript unit file.
.py - A Python unit file.
.svb - A VBScript unit file.
.sd - A DelphiScript unit file.
.scs - A C#Script unit file.
.scpp - A C++Script unit file.
Selenium or Unit Testing project item files:
Stores project item files:
Test Visualizer files:
|If the Bind Visualizer frames to SCC option is enabled, TestComplete automatically adds Visualizer files to the source control.
Note, that keeping Test Visualizer files in the source control is not recommended due to their large overall file size. Doing so can degrade performance of the check out and check in operations on your test project. For more information, see Visualizer Data and Source Control Systems.
User Forms project item files:
Web Services project item files:
Tested Applications project item files:
Note, that the following files are not added to the source code control:
.tcCFGExtender - This file holds tester-specific settings for the project suite (such as the workspace layout).
.tcLS - This file contains tester-specific settings for the project suite or project (such as local paths to tested applications, local values of project and project suite variables).
.bak - Backup copies of script units.
.tlb - This is a type library that contains declarations of events used in the project.
.tcLogs - This file contains information on the project suite or project logs.
Project item files that are physically located outside of the project suite folder.