Search:     Advanced search

TestTrack CVS Integration

Article ID: 534  |  Last updated: 29 Dec, 2014

TestTrack supports integration with CVS. See TestTrack Third-Party Integrations for supported versions.

This article includes information about how the integration works, creating a working directory and checking out files, setting up the integration, performing CVS actions in TestTrack, and troubleshooting.

Note: The following information applies to TestTrack 2014.1 and CVS 1.11.22. If you use a different TestTrack or CVS version, the steps to configure and use the integration should be similar.

How the integration works

TestTrack integrates with CVS by executing commands to the CVS.exe program. CVS.exe must be run globally because TestTrack cannot determine where the program is located. To run CVS.exe globally, either set up a path to CVS.exe in your autoexec file or make sure the path to CVS.exe is included in the Window PATH variable.

TestTrack uses the CVS log command to determine what files are located in the CVSROOT. This functionality can be tested from the DOS prompt.

The syntax depends on the authentication scheme being used by CVS. Following are two examples:


C:>CVS -d :pserver:JoeS@unixbox:/usr/cvsroot log

C:>CVS -d :pserver:JoeS@winbox/c//cvsroot log


C:>CVS -d :local:c:cvsroot log

Files must be checked into CVS for the log command to return information. Following is an example using the local authentication scheme.

C:>CVS -d :local:c:cvsroot import directory manufacturer tag

C:>CVS -d :local:c:cvsroot checkout directory

C:>CVS -d :local:c:cvsroot log

If the log command returns data about each checked in file, you are ready to use the TestTrack integration.

Create a working directory and check out files

Before the integration can be set up on the TestTrack side, you must set up a working directory and check out files from CVS to a working directory.

Setting up the integration

  1. In the TestTrack Client, choose Tools > Source Control Integration. The Source Control Integration dialog box opens with the Provider category selected.
  2. Select CVS from the Available providers list and click Make Current. CVS is displayed in the Current field.
  3. Select the Connection category.
  4. Enter the Project working path to the directory on your computer that contains your source files.
  5. Enter the Repository connection string. This string includes the authentication scheme, including username and computer if you use pserver, and CVSROOT path that are used to run the log command. This is the same connection string used in the DOS test, when running the CVS log command.
  6. Enter a CVS Password if CVSROOT requires authentication for access. If pserver is used, TestTrack first executes a login command, using the password, to authenticate the connection. TestTrack runs the CVS log command to retrieve file information after the connection is authenticated.
  7. Click Validate Connection. TestTrack validates the connection to CVS. If an error occurs, double-check the information you entered for the project working path, the repository connection string, and the password. You should also make sure you have checked out files to the specified working path.
  8. Select the Project Options category.
  9. 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.
  10. Select the Project Paths category.
  11. Expand the project tree, select the directories, and click Add. If you select the root directory, the user can access everything in the database. If you have a large database, and users require access to the entire database, you might want to select both root as a project path and the most commonly used directories. To limit the files that a user can access, select specific directories.
  12. Click OK to save the changes. CVS is now integrated with TestTrack.

Performing CVS actions in TestTrack

You can access the following CVS actions on the Source Files tab when editing TestTrack items:

  • Attach File—Attaches CVS files to the item.
  • Detach—Removes attached CVS files from the item.
  • Check Out—Retrieves a writable copy of the file to the working directory.
  • Commit—Submits changes to the CVS server from TestTrack. The version created by this commit is displayed in the Fixed Revision column on the item Source Files tab. Only available if the file has been modified and the changes have been saved.
  • View—Displays the contents of the latest version of the file in CVS.
  • History—Displays the entire history of the file from CVS.


Note: Products that extend CVS, such as CVSNT, may interfere with the integration.

TestTrack locks up when a CVS process locks up

After closing and restarting TestTrack, you cannot perform CVS functions in TestTrack. Sharing violations may occur with files in the TEMP directory. This occurs when CVS is locked up and has write locks on two temporary output files TestTrack needs. To resolve this issue, close TestTrack. Go to the Windows Task Manager and end all instances of CVS (cvs.exe) to free the temporary output files. Restart TestTrack.

Article ID: 534  |   Last updated: 29 Dec, 2014

Prev   Next
Visual Studio Cannot Load or Unload the TestTrack Add-in     TestTrack Outlook 2010 Add-in Does Not Work