TestTrack supports integration with Microsoft Visual SourceSafe (VSS). See TestTrack Third-Party Integrations for supported versions.
This article includes information about integration requirements, configuring the integration, performing VSS actions in TestTrack, and troubleshooting.
Note: The following information applies to TestTrack 2015.1 and VSS 2005. If you use a different TestTrack or VSS version, the steps to configure and use the integration should be similar.
The 32-bit TestTrack Client must be installed.
The VSS client must be installed and able to connect to the VSS database. The same connection as the client is used when setting up the connection information in TestTrack.
If the VSS database is on another computer, you must be able to access it via My Computer. When setting up the connection information, you will need to browse to the folder that contains the database folder. VSS must also be set as an SCC provider in the system registry.
Configuring the VSS integration
- In the TestTrack Client, choose Tools > Source Control Integration. The Source Control Integration dialog box opens with the Provider category selected.
- Select Microsoft Visual SourceSafe and click Make Current.
- Select the Connection category to enter the connection parameters that TestTrack uses to connect to the VSS database.
- Click Browse and locate the srcsafe.ini file. This file contains the path to the 'data' folder, which is where the database is located. Usually this is a relative path to the srcsafe.ini file. For example, your srcsafe.ini file may specify Data_Path = data. This means the database is in a folder named data, which is located in the same directory as the file.
- Enter the VSS project Username and Password.
- Click Validate Connection to test the connection to the VSS database.
- Select the Project Options category.
- Enter any Default check in comments. You can use field codes to automatically add issue-related information to check in comments. See the TestTrack help for information.
- Select the Project Paths category.
- Select the projects you want to be able to attach files from and click Add.
- Click OK to save the configuration.
Performing VSS actions in TestTrack
You can access the following VSS actions on the Source Files tab when editing TestTrack items:
- Attach File—Attaches VSS files to the item.
- Detach—Removes attached VSS files from the item.
- Get—Retrieves a read-only copy of the latest file version.
- Check Out—Retrieves a writable copy of the file to the working directory for editing.
- Undo Check Out—Removes the check out lock from VSS.
- Check In—Submits changes to a checked out file to the VSS database. The version created by the check in is displayed in the Fixed Revision column on the item Source Files tab.
- View—Displays the content of the latest version of the file in the VSS database.
- History—Displays the entire file history.
VSS is not in the Available Providers list when configuring source control integration
TestTrack cannot locate VSS as a source control provider. You must edit the registry to help TestTrack locate VSS.
- Using the Registry Editor (regedit), browse to the following registry key:
- 32-bit Windows—HKEY_LOCAL_MACHINESoftwareSourceCodeControlProviderInstalledSCCProvidersMicrosoft Visual SourceSafe
- 64-bit Windows—HKEY_LOCAL_MACHINESoftwareWow6432NodeSoureCodeControlProviderInstallSCCProvidersMicrosoft Visual SourceSafe
- Note the key’s string value. For example, SoftwareMicrosoftSourceSafe.
- Browse to the registry entry you noted.
- Make sure the following strings exist and point to the correct location:
- SCCServerName—String value is ‘Microsoft Visual SourceSafe’
- SCCServerPath—String value is the location of the VSS SCCI interface .dll on local hard drive. For example, C:Program FilesMicrosoft Visual StudioCommonVSSwin32SSSCC.DLL.