Repository considerations for a server project

To collaborate with other project stakeholders, you can open test assets from a local clone of a remote repository, pull project test assets from the remote repository, and push changes made to your local test assets to the remote repository. Before you add a project and then add a repository to that project, you must consider some information about repositories.

Consider the following sections about version control systems that are used to manage remote repositories.

The following types of Git-based version control systems are supported:
  • GitHub, which is an open-source product for storing and collaborating code.
  • Azure Repos, which is part of a solution of Azure DevOps, and focuses on collaboration between DevOps professionals to develop private code.

Both these version control systems support Git repositories to store code.

You must be familiar with the various aspects of these version control systems to manage the application code that you want to test in HCL OneTest™ Server.

You can learn more about installing, setting up, and using Git from the Git documentation.

You can learn more about installing, setting up, and using Azure Repos from the Azure Repos documentation.
Note: Git is the only tool that is supported to manage a repository in Azure Repos. Other tools, which can be used in Azure Repos, are not supported.

Git

You must install Git or upgrade to the supported version if you already have installed Git. See System Requirements.

Repositories and user identities

After you install Git, you must set up your Git repository and set up access for members. You must ensure that the repository contains your test assets.

Optionally, you can use a command line utility or Git tool to access the repository, upload your test assets, fetch or pull from the repository, push to the repository, clone the repository, and other operations that you want to perform in Git.

Local and shared repositories

After you create a remote or shared repository in Git, you can create a local version of the repository by cloning the remote repository. You must ensure that your test assets are available in the remote repository and are also cloned to the local repository.

Alternatively, if your test assets are on your local system, you can set up a Git repository in the bare mode, add the project files to the local repository, and then commit and push from the local repository to the remote repository in Git by using your preferred method.
Note: While copying the test assets from your local system to the repository, you must ensure that you copy the entire project that contains the test assets.

User authentication for the Git repository

The administrator can set up different types of authentications for accessing the Git repository. HCL OneTest™ Server supports the following authentication types:
  • HTTP with username and password
  • HTTP without username and password
  • HTTPS with username and password
  • HTTPS without username and password
  • SSH with SSH key and passphrase
  • SSH with SSH key and without a passphrase

Based on the authentication type that is set for a repository, you must provide the same authentication values in HCL OneTest™ Server when you add a repository.

Test assets

You must complete the following tasks in the desktop products where you author your test before you check in and commit the test assets to the Git repository.
Test type Task More information

API suite in HCL OneTest™ API

 Change the local stub to a remote stub. See Test run considerations for API Suites or API tests.
Add the library files.