Page tree

Skip to end of banner
Go to start of banner

Connecting to Source Control

Skip to end of metadata
Go to start of metadata

Supported Source Control Management Systems

Jtest ships with out-of-the-box support for the following SCMs:

BrandTested Version
Git1.7, 1.8, 1.9, 2.x
Mercurial1.8.0 – 3.6.3
Perforce 2006, 2012, 2013, 2014, 2015
Subversion (SVN)1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12, 1.13
Microsoft Team Foundation Server2012, 2013, 2015, 2017, 2018, 2019

Jtest relies on file paths that are consistent with the the environment where it is installed. If you are using a source control client installed as a Cygwin package on Windows, some Jtest features may not function properly due to Unix-style paths used in Cygwin.

Configuring Connection with SCM

Edit the .properties file located in INSTALL_DIR (or another location; see Configuration Overview for details) to connect to your SCM. Parameters will vary depending on the brand of your SCM. The following example shows the parameters required to connect to SVN:

• scontrol.rep.type=svn
• scontrol.rep.svn.url=https://svn_server/
• scontrol.rep.svn.login=username
• scontrol.rep.svn.password=password
• scontrol.svn.exec=C:\\path\to\svn.exe

See Source Control Settings for information about configuring your SCM connection.

The source-related settings must be properly configured to ensure that DTP has access to consistent data (see Sending Results and Publishing Source Code to DTP).

• No labels