Test Studio seamlessly integrates with Git based source control repositories to simplify the collaboration between QAs and developers. The Git integration can also facilitates the work of a QA team on the same test project, 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:
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 will be stored within that repo, and the overhead of downloading non-relevant items will be avoided.
Choose a Test Studio project, which you want to keep under source control in a Git repository and connect it to Git.
Anyone in the team, who need to work on that same project, can use the built-in option to connect to Git and open the project from the remote repository.
This action downloads from the remote repo a local copy of the project, which is connected to the remote source controlled project and all changes get tracked.
Find other useful topics for Git integration in Test Studio:
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.
The following applies to GitHub.com. Similar workflow is available in other remote repository providers.
Nowadays, two-factor authentication is used across different platforms to cover the increasing security policies. Git repositories are often subject of this type of user authentication. The concept of the Personal Access Token is designed to provide an option to connect to the platform programatically and you can use this in Test Studio instead of a password, which requires the second factor authentication.
The following workflow guides you how to create a personal access token (PAT) for a GitHub.com repository, which is accessed using two-factor authentication. 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.
3. Use the generated token to paste it instead a password in the Test Studio Connect to Git dialog.