Versions Compared

Old Version 1

changes.mady.by.user Anna Stuchlik

Saved on

compared with

New Version Current

changes.mady.by.user Anna Stuchlik

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space CPPTDESKDEV and version 10.3.3

...

  • Use file revision data from source control to determine authorship  (for automatically assigning test failures and policy violations to the responsible team member as well as for restricting test scope by author and/or modification time). See Configuring Task Assignment and Code Authorship Settings for details.
  • Update projects from source control before testing (if the Test Configuration’s Common> Source Control> Update projects setting is enabled).
  • Automate the preparation and tracking of code reviews (see Code Review).

...

In addition, you can use Parasoft’s source control API to add seamless integration with any other source control tool your team happens to be using. For details, see Adding a Custom Source Control Integration.

Note
titleSubclipse Support Notes
  • Each Subclipse plugin version is compatible with specific Subversion versions. Ensure that your Subclipse plugin is compatible with a version of Subversion that Parasoft supports. For example, you should not install Subversion 1.3 and Subclipse plugin 1.2, which uses Subversion 1.4. Subclipse 1.4.x requires Subversion 1.5.0 version of JavaHL/SVNKit. Subclipse 1.4.5 already has subversion client adapter 1.5.2.
  • Due to changes introduced in Subversion 1.4, Subversion clients earlier than 1.4 cannot work with working copies produced by Subversion 1.4. If you are using Subclipse plugin 1.2 (which includes Subversion 1.4), you might receive the following error message:
    svn: This client is too old to work with working copy '.'; please get a newer Subversion client
    This means that Parasoft is using a command-line client that is version 1.3 or older. The solution is to update your command-line SVN client to version 1.4. The client version can be verified by executing svn --version

...

Properties tab

  • User: Enter the Serena Dimensions login name.
  • Password: Enter the Serena Dimensions password.
  • Server: Enter the Serena Dimensions server host name.
  • Database name: Enter the name of the database for the product you are working with.
  • Database connection: Enter the connection string for that database.
  • Server locale: Select the language.

Workset Map tab

If the project has been downloaded/moved to a location other than default work area, use this tab to specify a mapping between the project (or stream) with the Serena repository and the local project.

If you are working in the default work area, you do not need to define mappings.
 


Enter an expression that maps workspace resources to Serena Dimension repository paths.

  • Example 1: If you use scontrol.rep.serena.mapping_1=${project_loc\:MyProject};PRODUCT1\: WORKSET1;src\\MyProject, then Project 'MyProject' will be mapped to the Serena workset PRODUCT1:WORKSET1  and workset relative path: src\\MyProject
  • Example 2: If you use scontrol.rep.serena.mapping_2=${workspace_loc};PRODUCT1\:WORKSET1 then the complete  workspace will be mapped to the Serena workset PRODUCT1:WORKSET1.

StarTeam Configuration

To use StarTeam with C++test ensure that:

  • Ensure that you have the Borland StarTeam SDK installed. This can be downloaded for free from the Borland web site.

For Visual Studio plugins, Parasoft StarTeam support is available for VS 2005 and VS 2008. When you are enabling source control support, specify the following repository properties:

  • Server: Enter the StarTeam server’s machine name or IP address.
  • Port: Enter the StarTeam server’s port.
  • User: Enter the user name under which you want to connect to the repository.
  • Password: Enter the password for the above user name.
  • Paths lookup> StarTeam Path: When working with large multi-project repositories, you can improve performance by specifying the project, view, or folder that you are currently working with. You can indicate either a simple Project name (all views will be scanned when searching for the repository path), a Project/View (only the given view will scanned) or Project/View/Folder (only the specified StarTeam folder will be scanned).
  • Paths lookup> Working Folder: If the StarTeam Path setting specifies a StarTeam view or folder, you can use this field to indicate a new working directory for the selected view's root folder (if the path represents a view) or a new working directory for the selected folder (if the path represents a folder).

Subversion Configuration

Parasoft’s Subversion support is based on the command line client 'svn'. To use Subversion with C++test, ensure that:

  • The Subversion 1.2.x, 1.3.x,  1.4.x, 1.5.x, 1.6.x, 1.7.x, or 1.8.x client is installed.
  • The client certificate is stored in the Subversion configuration area. The Subversion client has a built-in system for caching authentication credentials on disk. By default, whenever the command-line client successfully authenticates itself to a server, it saves the credentials in the user's private runtime configuration area—in ~/.subversion/auth/ on Unix-like systems or %APPDATA%/Subversion/auth/ on Windows.

When you are enabling source control support, specify the following repository properties in the Create Source Control Description dialog:

  • URL: Enter the URL for the SVN server. The URL should specify the protocol, server name, port and starting repository path (for example, svn://buildmachine.foobar.com/home/svn).
  • User: Enter the user name under which you want to connect to the repository.
  • Password: Enter the password (not encoded) for the above user name.

Synergy Configuration

Synergy 7.0 introduces a new, faster way of working called Web mode. C++test supports both of the following Synergy/CM communication modes:

...

  • Web mode (since Synergy 7.0)
  • Traditional mode

    • When you are enabling source control support, specify the following repository properties in the Create Source Control Description dialog:

    ...

  • Database path: Enter the absolute Synergy database path.
  • Engine host: Enter the Synergy server’s machine name or IP address. For Web mode, the host must be a valid Synergy Web URL with protocol and port (e.g., http://synergy.server:8400).
  • User: Enter the user name under which you want to connect to the repository.
  • Password: Enter the password for the above user name.
  • Use remote client (UNIX systems only): Enable this option if you want to start CCM as a remote client session. This is not used for Web mode.
  • Local database (remote client): Enter the path to the location where the database information is copied when you are running a remote client session. This is not used for Web mode.

    • Team Foundation Server Configuration

    ...

    By default, C++test uses the cached credentials for accessing TFS (this could be your user login or some previously logged in information). You can provide custom credentials if you want to use them instead of the cached ones.

    Visual SourceSafe Configuration

    ...

  • VSS Database Path: Enter the database path (the location of SRCSAFE.INI).
  • User: Enter the user name under which you want to connect to the repository.
  • Password: Enter the password for the above user name.
  • Project root in repository: Enter the project root. This begins with $/; for example, $/nightly_test.

    • Specifying Source Control Definitions via localsettings

    Source control definitions can be specified in localsettings (e.g. for sharing team-wide settings via  DTP or specifying options at the command line). See Configuring Localsettings for details.