...

1. Make sure that the command line client for the given source control is on the system%PATH%/$PATH and is available when SOAtest is launched.

   • For example, if you have Subversion, it is not sufficient (or even required) to install the Subclipse plugin to Eclipse (SVN Eclipse plugin). Instead, you should have the plain command line svn.exe Subversion client.

2. Choose Parasoft> Preferences. The Preferences dialog will open.
3. Select Parasoft> Scope and Authorship in the Preferences dialog.
4. Check Use source control (modification author) to compute scope.
5. Select Parasoft> Source Controls in the Preferences dialog.
6. If the appropriate repositories are already set (refer to the auto-configuration process described in Configuring SOAtest Across TeamsPreferences Overview), enter your user and password, and specify the path to your source control client executable (if it is not already on your system path).
   
   If the appropriate repositories are not already set (refer to the auto-configuration process described in Configuring SOAtest Across TeamsPreferences Overview) specify them as follows: 
   1. Enable the source control system you want to use and specify the path to the SCM client executable. You do not need to specify the executable path if it is already on your system path.
   2. Click New in Repository properties field and enter the source control properties required for the selected type of source control system.  
   3. Click OK to close the Source Control Description dialog.
7. Apply your changes and click OK.

...

Subversion Configuration

Parasoft’s Subversion support is based on the command line client 'svn'. See About Source Control Support for a list of supported SVN versions.

The client certificate must be 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.

Team Foundation Server Configuration

...

By default, SOAtest 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.

Specifying Source Control Definitions via localsettings

...