Borland® StarTeam® 2008 Synchronizer for TestDirector for Quality Center Release Notes

This file contains important information that may not appear in the online Help. Read this file in its entirety.

System Requirements/Prerequisites

StarTeam TestDirector for Quality Center Synchronizer has been tested on Windows Server 2003 SP2 (32-bit version). It is recommended that you install the Synchronizer on the same computer on which the TestDirector for Quality Center database resides, unless that is not a Windows platform. Because of the OTA APIs, the Synchronizer must run on a Windows operating system. It has no unusual operating system requirements.

• The Enterprise or Enterprise Advantage edition of the StarTeam Server for Windows (2006 or 2008)
• TestDirector for Quality Center 9.0 or 9.2
• A Java Runtime Environment (JRE), version 1.5.0_09 or later

The software listed above does not need to be located on the same machine as the Synchronizer, which can, if desired, run on a separate machine. However, the Synchronizer must have network access to the TestDirector for Quality Center database and the StarTeam Server.

Installation Instructions

To install the Synchronizer, run the file ST_TD_Synchronizer.exe and follow the onscreen directions. ST_TD_Synchronizer.exe is a self-extracting executable that, by default, creates a folder named StarTeam TestDirector Synchronizer in your Temp folder. It also adds files like setup.exe, which automatically installs the integration files and runs the self-extracting executable StarTeam-runtime.exe. StarTeam-runtime.exe installs the StarTeam SDK, which enables the integration to access the StarTeam Server.

If you are using the StarTeam Server for Windows and installing over a previous version of the Synchronizer, the installer renames the following files to preserve any changes you might have made to them:

• BugSync.ini becomes BugSync.000
• run.bat becomes run.000
• run-again.bat becomes run-again.000

Known Issues

The following are known issues in StarTeam TestDirector for Quality Center Synchronizer.

• Large synchronizations may result in out of memory errors. In these cases, we recommend adding -Xmx256m (or up to -Xmx1024m, depending on available resources) to the following line in run.bat or run-again.bat.

  %JAVA% -classpath "%_CLASSPATH% com.starbase.mtdsync.App BugSync.ini

  such that it reads:

  %JAVA% -Xmx256m -classpath "%_CLASSPATH% com.starbase.mtdsync.App BugSync.ini

• If the LookupList field value is also the name of the list, the Synchronizer will not create that value in the corresponding StarTeam enumerated field, but instead generates an error. The work around is to manually add the value to the actual list in TestDirector for Quality Center.
• The 2005 R2 Synchronizer allowed an empty TestDirector for Quality Center field mapped to a StarTeam enumeration to result in the StarTeam enumeration having an empty value. This was accomplished by setting the value of the StarTeam enumeration to 0 or -1. T his functionality has been removed because these values are not allowed by the StarTeam client . If the TestDirector for Qualtiy Center value is empty and is mapped to a StarTeam enumeration, the default value of the enumeration in StarTeam will be used. Even if the mapping is owned by TestDirector for Quality Center, if the value in StarTeam is empty, the StarTeam change request will be updated with the default value. In the 2005 R2 Synchronizer, if the vts_create_custom_fields directive was used to create an enumeration field in StarTeam, these newly created enumeration fields did not have the default value correctly set. If such a property is encountered during synchronization, a warning message is generated indicating that the user should use a 2006 or later client and set the default value in the customize dialog. If a TestDirector for Quality Center field is mapped to a StarTeam enumeration and that TestDirector for Quality Center field allows blanks, a warning is generated indicating that the user should customize the TestDirector for Quality Center field to make it "Required" in TestDirector.
• TestDirector for Quality Center does not convert times to local time when the TestDirector for Quality Center server is running in a different time zone than the Synchronizer, so times must be translated into the time zone of the server. TestDirector now performs the translation based upon a time zone ID code that specifies the time zone of the TestDirector server.

What's New

The following features are new:

• Support for four new Test Director for Quality Center fields in Releases and Cycles:
  • Detected in Cycle (DETECTED_IN_RCYC)
  • Detected in Release (DETECTED_IN_REL)
  • Target Release ((TARGET_REL)
  • Target Cycle ((TARGET_RCYC)
• Support for Test Director for Quality Center verifed fields.
• Support for Test Director for Quality Center multi-value fields.

• When multiple iterations are defined, a change request is moved in StarTeam from its current location to the root folder of the correct iteration if the Synchronizer detects that the change request must belong to a different iteration based on its associated TestDirector for Quality Center properties. This move functionality is turned on by default, but can have significant memory overhead. Use the new directive VTS_ENABLE_MOVE_CR_CAPABILITY to turn off the move functionality.

• If the move functionality is required, the Synchronizer and server memory can be held to a minimum, at the cost of slower performance and server overhead, by keeping a single StarTeam view open at a time. The option to keep a single view open at a time is turned on by default. Use the new directive VTS_KEEP_ONLY_ONE_VIEW_OPEN to turn off this option.

Copyright © 2008 Borland Software Corporation. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners.