This topic explains how to build a custom integration to any source control system. In this section:

Introduction

SOAtest has  Parasoft Test provides builtin support for most common version control / source control systems,   as described in such as SVN and Git. See Connecting to Your Source Control Repository for details. In addition, it provides Additionally, SOAtest includes an open Source Control API, which allows other source control tools to be integrated with Parasoft Test.

In this section:

Adding a Custom Source Control Implementation

API Javadoc (Eclipse only)

SOAtest.

API Javadoc

The The web-based help system provides a Source Control API topic that includes includes an open_api_javadoc.zip file containing Javadoc documentation for all classes and interfaces that must be implemented. The Javadoc is located archive file is located in the <INSTALL>\/plugins\/com.parasoft.ptest.sourcecontrol.eclipse.core\javadoc /openapi/ directory.

Main Interfaces

...

The source control API and all related classes are located in the sourcecontrol.jar file located in the <INSTALL>\/plugins\/com.parasoft.ptest.libs_<VERSION>/Parasoft / directory.

Before you can compile, you may need to add the following additional jar files to your classpath:

...

All JAR files are located in the <INSTALL>\/plugins\/com.parasoft.ptest.libs_<VERSION> directory.

...

1. Create a single jar file containing all of the required classes. There are no specific rules concerning the jar file name or package names etc.
2. Copy your jar file into the <INSTALL>\/plugins\/com.parasoft.ptest.sourcecontrol.eclipse.core\/ext directory and restart SOAtest.
3. Verify the implementation as follows:
   1. Choose Parasoft> Preferences> Source Control and disable the Use DTP settings option.
   2. Verify that an option for your implementation name appears among the builtin version controls.
   3. Enable the option for your implementation and click New. 
   4. Add the required properties, and click Apply.
   5. Choose Preferences> Scope and Authorship and verify that Use source control to compute scope is enabled.
   6. Open a file controlled by your version control system and right-click anywhere in the file’s source code
   7. Choose Show author at line. You should see valid version control author information.

...

SOAtest ships with a sample implementation for the Source Control Open API. A zipped package is located in <INSTALL>\/plugins\/com.parasoft.ptest.sourcecontrol.eclipse.core_<VERSION>\/openapi\/demo\.

Create the following directory structure after extracting the open_api_demo.zip file:

...

You can compile and deploy it using the procedures described in the preceding section.

To play interact with the demo:

1. Deploy the demo.jar file.
2. Unpack the local repository to any location.
3. Restart your Parasoft Test product.
4. Import the demo local repository project into your workspace.
5. Under Parasoft> Preferences> Source Control, enable the demo implementation.
6. Open a file, right-click anywhere in the file’s source code, then choose Show author at line. You should see valid version control author information.