Integration with Git Source Control Systems

Test Studio seamlessly integrates with Git based source control repositories to simplify the collaboration between QAs and developers. The Git integration can also ease the work of multiple users on the same test project in a QA team, allowing them to check-in their work at the same time, but independently.

These are the steps to connect and use a Test Studio project stored in a remote Git repository:

1. Create a dedicated empty repository in the selected Git platform.

   Note: Our recommendation is to use an empty repo to connect the Test Studio project to. This way only Test Studio-related artifacts get stored within that repo, and the overhead of downloading non-relevant items is avoided.

2. Choose a Test Studio project, which you want to keep under source control in a Git repository and connect it to Git.

3. Anyone in the team, who need to work on that same project, can use the built-in option to open the project from the remote repository.

   Note: This action is equal to clone a repo and downloads a local copy of the project, which is connected to the remote source controlled repository and all changes get tracked.

4. Below are other useful topics for Git integration in Test Studio:

• Supported Git commands

• Branch Management for Git repos

  Important
  
  Test Studio provides general support for git repositories -this includes commit, push, pull and revert commands.
  
  Test Studio does not provide any means for creating a repository in a remote provider. Instead, it leaves it up to you to decide in what remote provider you want your projects stored. Having that in mind, you must first create an empty remote repository in a remote provider of choice, and only then connect a local project to that repository using Test Studio.
  
  If an attempt is made to connect a local project to a remote repository, in which there is an existing project, you need to manually merge and resolve the conflicting project files.

Create Git Remote Repository

The following applies to GitHub.com. Similar workflow is available in other remote repository providers.

Using Personal Access Token for Authentication in Git Repo

The concept of using the Personal Access Token is designed to provide an option to connect to the platform programmatically and we strongly recommend you to use this option for authentication in Test Studio instead of a password.

Important

We strongly recommend to generate a PAT (Personal Access Token) scoped for accessing the testing project repository only.

The following workflow guides you how to create a personal access token (PAT) for a GitHub.com repository. Then, that personal access token is used instead of the user password, when connecting to GitHub through Test Studio:

1. Open your GitHub account and navigate to its section Settings -> Developer settings.

2. Switch to Personal access tokens section and use the Generate new token button to create one.

   Important
   
   We strongly recommend to generate a PAT (Personal Access Token) scoped for accessing the testing project repository only and use it to connect to the remote repo.

3. Use the generated token to paste it instead a password in the Test Studio Connect to Git dialog.

   Note: The example shows creating a PAT in Github.com. If not using this platform to store the repository, please, follow the provider's guidelines for creating a PAT.