Requirements and Prerequisites

Applies to TestComplete 15.40, last modified on March 25, 2022

Before you bind your project suite to your Subversion repository, prepare your test computer and TestComplete for integration.

Preparing Test Computer

To work with the Subversion source control system from TestComplete, the following software must be installed on your computer:

  • CollabNet Subversion 1.8.x for Windows - TestComplete uses the SVN command-line utility (svn.exe) to work with the Subversion source control system.

    You can download the utility from here:

    Currently, TestComplete supports integration only with the 32-bit version of the Subversion source control system.
  • TortoiseSVN (Recommended) - A free Subversion client that you can use to work with Subversion from TestComplete.

    You can download the client application from here:

Preparing TestComplete

  • Make sure that the Subversion plugin is enabled in TestComplete (it is installed and enabled by default when you install TestComplete).

    If you experience any issues with Subversion integration in TestComplete, select File > Install Extensions from the TestComplete main menu and enable the Subversion plugin.

  • Configure TestComplete to integrate with Subversion:

    1. In TestComplete, select Tools > Options from the main menu and then select Source Control from the tree on the left side of the resulting Options dialog.

    2. In the Current source control plugin list, select Subversion Plugin.

    3. In the Path to SVN box, enter the valid path to the SVN command-line utility executable (svn.exe).

    4. (Recommended) If you have the TortoiseSVN client application installed on your computer, select the Use TortoiseSVN client check box to work with your Subversion repository from TestComplete.

Preparing Your Test Projects

If your test project is already bound to Subversion by using the deprecated SmartBear SVN provider (TestComplete versions prior to version 11), migrate that project to the new Subversion Plugin. For instructions, see Migrating From Legacy SCC API Providers.

See Also

Integration With Subversion
Migrating From Legacy SCC API Providers

Highlight search results