Selecting a Source Code Control Provider

Microsoft Source Code Control (MSSCC)-Based Providers

TestStand supports several third-party source code control (SCC) providers. Available SCC operations in TestStand are the same regardless of the third-party provider you select. Specific support or functionality for each operation varies by provider.

In some cases, you might decide to use a specific SCC provider because your company has standardized on that application. If not, you must decide which provider you want to use for managing files. Consult the SCC administrator at your company to find out if you must use a specific provider.

After you select and install an SCC provider, you must configure TestStand to work with that provider. You can configure a TestStand workspace to work with only one SCC provider at a time.

TestStand integrates with any 32-bit SCC provider that supports the Microsoft Source Code Control Interface. 64-bit TestStand supports 32-bit SCC providers only and does not support 64-bit SCC providers.

NI supports the following third-party SCC providers with TestStand:

• Helix Core
• SVN (PushOK plugins)

The following third-party SCC providers are allowed but not supported:

• IBM Rational ClearCase
• MKS Source Integrity
• Serena Version Manager (PVCS)
• Microsoft Visual SourceSafe

Git-Based Providers

The TestStand Sequence Editor supports source code control using Git-based providers through the Git pane. You can connect to your Git repositories and perform common version control operations using the Git pane, and can also work with local Git repositories without using a Git provider. You can use the Git pane to work with any source folder in a Git repository without the need to create a TestStand workspace file.