Repository considerations for a server project

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

Consider the following sections about using Git repositories with HCL OneTest™ Server. For more information about installing, setting up, and using Git, see the Git documentation.

Git

You must install Git or upgrade the version if you already have installed Git.

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 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 authentication for accessing the Git repository. HCL OneTest™ Server supports the following authentication types:
  • HTTP with user name and password
  • HTTP without user name and password
  • HTTPS with user name and password
  • HTTPS without user name 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 client where you are authoring your test before you check in and commit the test assets to the Git repository.

Desktop client tasks for each test type to complete before checking in and committing 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.
Add the library files.