Integrating ZebraTester with GIT

 

GIT Integration with ZebraTester

Introduction

By using the GitHub integration you can manage all of your recorded sessions and all of your load test results with a remote revision control system. This allows you to have multiple branches of the MyTests directory tree, and to track changes/modifications of any file. Furthermore, the content of old, overwritten files can also be restored.

Server Configuration:
GitHub-integration supports HTTPS and ssh based connections, and both public and private repositories can be configured to be used with the GitHub integration.

Please refer to the attached GitHub Integration Manual for a complete guide on setting up the connection.

Supported Operations:

  • Git Status: This will list down all the changed files. Beneath the list, there is an option to make the files staged.

  • Commit: After providing the Commit Message the files will be committed.

  • Push: All the committed changes will be pushed to the Git Server.

  • Fetch: Fetch gathers any commits from the target branch, that do not exist in your current branch and stores them in your local repository. However, it does not merge them with your current branch.

  • Pull: This will make the local branch up-to-date with its remote version, and automatically merges the commits without letting you review them first.
    Please closely manage your branches, you might run into frequent conflicts otherwise.

  • Merge: Join two development histories together. "Might Lead to Conflicts, Please refer to Git Documentation ".

  • Copy: For making a copy of the current Branch.

  • Clone: This will make a copy of the Remote Branch, and it's possible to have a different name from the parent remote branch.

  • Delete: This will delete the branch from the local repository only.

  • History: A utility function to display the commit history of the current branch.

Connecting to a GitHub Repo

Step

Screenshot

Step

Screenshot

Open the Project Manager from the Main ZT Screen

Click the GitHub Icon

Fill in the means your organization uses to connect to your Github Server.

  1. HTTPS

    1. Git Repository HTTPS Path

    2. User Name

    3. Password

  2. SSH Connection

    1. Git Repository

    2. SSH key

    3. Passphrase

  3. Proxy Settings

    1. Check the box if Using an Outbound HTTP(S) Proxy for accessing the GIT Server

      1. Proxy Host  

      2. Proxy Port  

      3. Proxy User Name  

      4. Proxy Password

 

Can't find what you're looking for? Send an E-mail to support@apica.io