TestTrack supports integration with Perforce SCM. See TestTrack Integrations for supported platforms and versions.

This article includes information about the integration requirements, configuring the integration in TestTrack, performing Perforce actions, and troubleshooting.

Note: The following steps were tested using TestTrack 2012.1.0 and Perforce 2011.1.

Requirements

The Perforce client must be installed and able to connect to the Perforce server. TestTrack uses the same server connection information as the Perforce client.

Configuring the integration

1. In the TestTrack Client, choose Tools > SCC Integration. The Configure SCC Integration dialog box opens with the Local Options category selected.
   
   
2. Select Perforce SCM and click Make Current.
3. Select the User Options category.
   
   
4. Enter the Perforce server and port number in the Server:Port field. For example, Server1:1666.
5. Enter the Perforce workspace name without the path in the Workspace field. For example, if the workspace is located in C:\Users\username\p4server_1666\my_workspace, enter my_workspace.
6. Enter the Perforce Username and Password and click Validate Connection. TestTrack verifies the Perforce connection.
7. Select the Project Options category.
   
   
8. Optionally enter a Check In Comments Template. You can use field codes to automatically add issue-related information to check in comments. Refer to the TestTrack User Guide for information.
9. Select a Perforce File Attach Option.
   • Select Retrieve all files at once to retrieve all files from the Perforce server at the same time. Use this option only if you are connecting to a small-to-medium Perforce server.
   • Select Retrieve files by directory to retrieve file listings for Perforce folders as you select them. Use this option to improve performance if you are connecting to a large Perforce server.
10. Select the Project Paths category.
    
    
11. Expand the Branch tree, select a depot, and click Add. Users can access all files in the Perforce database if you select the root depot. Select specific depots to limit files users can access.
12. Select the Check In Options category.
    
    
13. Select Include options to enter fix event on check in to allow users to add a fix workflow event when checking in files.
14. Select the Event to use.
15. Click OK to save the configuration.

Performing Perforce actions in TestTrack

• Attach File—Attaches source code files to TestTrack items.
• Detach—Removes attached Perforce source code files.
• Sync—Retrieves a read-only copy of the latest file version from Perforce to the workspace. Checked out or locked files are not retrieved.
• Submit—Submits changes to Perforce. You can only submit files from the default Perforce changelist. If you are submitting files attached to an issue, click Submit & Fix to also move the issue to the Fixed state after the changes are submitted. The file version number in the Fixed Revision column is updated after changes are submitted.
• Open for Edit—Retrieves a writable copy of the file to the workspace for editing. You must open the file in the editor from the workspace to make any changes.
• Revert—Cancels the open for edit action.
• View Local Copy—Displays the content of the latest version of the selected file on the Perforce server.
• History—Displays the entire history of the selected file from the Perforce server.

Troubleshooting

SCC project has not been successfully opened Perforce error

The Perforce login credentials are invalid based on the Perforce security level. TestTrack does not support level 3, or ticket-based, security with the Perforce integration. If the Perforce server is configured to run the auth-check trigger to integrate Perforce with an Active Directory or LDAP server, which enforces level 3 security, the integration does not work.

Perforce integration stops working

Use the following p4 commands to ensure Perforce is working correctly. If the commands fail, refer to the Perforce documentation for information.

1. Enter p4 info from a command prompt to verify your Perforce username, client name, and client root path are current. If this command does not run correctly, you cannot use Perforce commands in TestTrack.
2. Enter p4 fstat/ from a command prompt to verify specific file information, including the local path, current status, and latest revision. For example, you can enter p4 fstat //depot/mydocs/design.doc to see if Perforce can retrieve the design.doc information. If this command does not work correctly, fixed revision numbers and timestamps are not updated when changes are submitted from TestTrack.

The TestTrack Attach Files dialog box opens slowly or does not open

1. In TestTrack, choose Tools > SCC Integration.
2. Click the Project Options category.
3. Select the Retrieve files by directory.
4. Click OK to save the changes.

The TestTrack Attach Files dialog box is empty

1. Enter p4 dirs from a command prompt to update the folder structure from the Perforce server.
2. Enter p4 file from a command prompt to update the list of files for a specific Perforce folder.

A Request too large error occurs

A Perforce command is returning the maximum number of allowed results. The maximum results limit is enforced when the Retrieve all files at once file attach option is selected in the TestTrack SCC integration project options. The maxResults and maxScanRows limits can be reconfigured using Perforce groups. Ask your Perforce administrator for information.

Additional troubleshooting help

When Perforce commands are executed, the output is generated to a text field in the temporary directory. You can use this output to help troubleshoot integration issues. Enter set temp from a command prompt to locate the temporary directory. In the temporary directory, open the ttproscc.txt file to view general output generated from Perforce commands or the ttsccerr.txt file to view Perforce command errors.