Forum Discussion

G-wagon's avatar
G-wagon
Regular Contributor
2 months ago
Solved

Gitlab OR Tortoise

Hi

We are in a process of implementing a version control tool for our automation needs. I am bit confused based on what I've read on TestComplete documentation on Native Clients.

Now, my question here is that what's the difference between Gitlab & Tortoise in specific to using it with TestComplete. Are they both native client ? If we get GitLab(which we are inclined towards), do we still need TortoiseSVN, TortoiseGit or TortoiseHg ? If yes, under what specific scenarios we'll need to use Tortoise?

Thanks in advance for addressing my query above.

 

6 Replies

Sort By
  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    2 months ago
    Copy Link

    GitLab is a comprehensive DevOps platform that integrates various tools and functionalities to streamline the software development lifecycle. 

    GitHub is a proprietary developer platform that allows developers to create, store, manage, and share their code

    TortoiseGit is a free open-source client for the Git version control system

    TortoiseSVN is a Revision control / version control / source control software for Windows

     

    If you search the internet, you can find Pros and Cons between them. TC supports only https://support.smartbear.com/testcomplete/docs/working-with/integration/scc/index.html  and the client plugin may not support all the features, such file compare, labelling, versioning etc. it will usually have basic operations such as check-in/out files.

     

     

    • G-wagon's avatar
      G-wagon
      Regular Contributor
      2 months ago
      Copy Link

      Do you mean that one will need both the tools to be used with testcomplete ?

      • ChrisKibble's avatar
        ChrisKibble
        Occasional Contributor
        2 months ago
        Copy Link

        I'm using Github with my projects. Under the hood, when either Github or Gitlab, TestComplete is calling on your locally installed version of git.exe and appending the necessary parameters based on what options you pick. 

        Here is an example of a pull that I just did on my project. You can see it's just using the command line it builds based on what I pick.

        The TC options seem to support all of the basic stuff (pull, push, commit, fetch, branches, resets, etc.), but when you need to do something other than that, you'd either go back to the UI, or the command line GIT.EXE. 

        For example, I don't see a way to create a version or a release within the TestComplete UI, even though those are certainly supported by GIT.EXE and GitHub. If I wanted to do that, I'd do it outside of the test environment. Which makes sense, you don't need TC to manage the overall repo, you just need it to be able to pull/commit/push.

        Hope this makes sense.