Forum Discussion

mrouse's avatar
mrouse
Contributor
13 years ago

TestComplete and Subversion

Hi everyone,



I am hoping someone has had a similar issue with TestComplete configuration files and Subversion.  I am having a hard time with the test complete config files like the TCCFGEXTENDER file and the way Subversion handles the changes.  I am on a team with 3 other programmers and thus we each have a TestComplete License.  As we create and change our scripts along with the generated  TC logs the TC configuration files change as well, and so Subversion wants me to resolve the conflicts in these configuration files.  The problem is that the TC configuration files are very cryptic and I don't know what or how to make changes to these files.



Any thoughts would be of great help.



Thanks,



Mike  
  • ray_mosley's avatar
    ray_mosley
    Frequent Contributor
    13 years ago
    Mike and I work for the same company, and are dealing with the issue of saving TestComplete project suites and projects.  So many files are changed each time that are completely unrelated to the single script you are attempting to debug.  If you attempt to reload the project from the repository, you get many conflicted files from Subversion.  I suspect the issue would be the same for any other source control repository (like ClearCase).

    After I have made some changes to my local copy of the repository (changing a script as I debug, and rerunning it), I have log files, objects, and alias that are now in conflict when I attempt to reset TestComplete to a known location.  When the conflicts exist from the source control system, the project is unavailable to TestComplete.  I am now dead in the water.

    What is the solution to archiving TestComplete projects in a source control system?

  • AlexeyKryuchkov's avatar
    AlexeyKryuchkov
    SmartBear Alumni (Retired)
    13 years ago
    Hi Micheal and Harlan,



    Please refer to this and that threads. I hope the information from them answers all of your questions.
  • ray_mosley's avatar
    ray_mosley
    Frequent Contributor
    13 years ago
    The RTFM responses caused us to go and read your documentation about using TC with source control systems.  I very soon ran up against another issue.  You documentation says:



        "Select File | Source Control | Add Project from TestComplete’s main menu. This will call the Select SCC Provider dialog that lists source control systems installed on your computer. TestComplete generates this list automatically."



    Our list is empty. I have the TortoiseSVN client on my system, but the list ifs empty.  How does TestComplete generate this list, and how do I correct it to add our TortoiseSVN repository?

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    13 years ago
    Hi Harlan,



    As it is said in the documentation and threads referred to by Mike, TestComplete can interact only with the source control systems (SCS) that support MS SCC API. SVN client itself does not support it and you need to look for and install the provider like Tam Tam, PuskOK or some other one that add MS SCC API support to SVN client. You should see the relevant provider in the SCC providers list as soon as this support is added.
  • ray_mosley's avatar
    ray_mosley
    Frequent Contributor
    13 years ago

    I have removed TortoiseSVN from my system where TestComplete resides.  My environment is installed evaluation copy of TamTam SVN 3.3.0 and CollabNet SVN client 1.7.4.

    I saved a small project suite from the repository in a new directory outside my working repository area, and renamed it uniquely.  I modified some scripts, ensured it ran, and then tried to add the project to the repository from the new directory.  My process was:



    1. File->Source Control->Add Project Suite

    2. The SCC Dialog appearred with

      TamTam as the only option

    3. Entered path to the svn.exe command line interface

      (from Collab.net)

    4. Entered the reportory address

    5. Verified Connection (all

      was fine)

    6. selected OK

    7. Got first of 20 error windows (see attachment ending

      in 01)

    8. selected OK

    9. Got second of 20 error windows (see attachment

      ending in 02)

    10. selected OK to all the other error windows

    11. ...


    result: nothing added to repository, but the File->Source Control option "Add Project Suite" is disabled, but the "Add to Source Control" is disabled.

    QUESTIONS:



    • What is wrong with my setup?

    • What is the actual process to save new projects

      (outside working copy of repository) to the repository?

    • What is the actual

      process to save modified existing projects (inside or outside working

      copy of repository) to the repository?


  • ory_z's avatar
    ory_z
    Contributor
    13 years ago
    Not sure about your specific problem but just wanted to give you a heads up that TamTam does not seem to have been developed since May 2010 (that's version 1.30 which is the latest as far as I can tell. Which version are you using?)

    I am extremely skeptical that it can interact with SVN 1.7 since the way the local copy is stored has changed.



    In a way we are in the same boat, we have been using PushOK until now relatively successfully however it too does not support SVN 1.7 (they released an RC but it is not working for us). For now what we are doing is running 1.6.16 client on our machines, it connects ok to the SVN Server (which is 1.7).

    However we are on the lookout for plugins supporting 1.7 and that's how I have reached this thread (no luck so far).
  • ray_mosley's avatar
    ray_mosley
    Frequent Contributor
    13 years ago
    Check out AgentSVN; that team has been good at working with us to get it working, BUT we are currently at an impasse with what might be Automated QA's implementation of the MSSCCI interface.  Stay tuned...
  • jussij's avatar
    jussij
    New Contributor
    13 years ago

    In response to Harlan Mosley:


    >> Check out AgentSVN;


    AgentSVN is a Subversion client that implements the MSSCCI so in theory it should work with TestComplete.


    I spent some time working with Harlan trying to get AgentSVN to work with TestComplete and we did in fact get some way to making this work.


    For anyone that might be interested the following version of AgentSVN does work to some extent with TestComplete:


    http://www.zeusedit.com/agent/bin/asvn-beta.zip


    NOTE: For AgentSVN to work you also need to have installed the Subversion command line tools found here:


    http://sourceforge.net/projects/win32svn


    >> that team has been good at working with us to get it working


    The version above does in fact work to some extent with TestComplete.


    To see how it works you would need to do the following:


    1) Configure AgentSVN to point to a local SVN respository using the SVN file protocol.


    2) AgentSVN will then ask for permission to create the local SVN respository. Answer yes.


    3) Create a simple local TestComplete project suite containing one project.


    4) Inside TestComplete add that project suite to source control


    5) Ignore the file locked message and hit the overwrite option.


    6) Check in the project suite


    >> BUT we are currently at an impasse with what might be Automated QA's implementation of the MSSCCI interface.


    Unfortunately during this initial testing I did come across what appears to be a fairly major issue :(


    Having successfully created the above test suite and imported it into Subversion, I then tried to add a new project to this test suite.


    Unfortunately that operation failed with a TestComplete MSSCCI error.


    I then tried to add and existing project to the test suite but it failed with the same MSSCCI error.


    Suspecting this might well be an AgentSVN issue I did some more investigation into the issue.


    After further investigation I suspected the issue might in fact be with TestComplete itself.


    To confirm this I repeated the whole process but this time connecting TestComplete with Microsoft Visual Source Safe and sure enough ran into the exact same MSSCCI error.


    From what I can tell it appears TestComplete is not correctly implementing the MSSCCI SccAdd function:


    http://msdn.microsoft.com/en-us/library/bb165463.aspx


    Cheers Jussi Jumppanen

  • AlexeyKryuchkov's avatar
    AlexeyKryuchkov
    SmartBear Alumni (Retired)
    13 years ago
    Hi Jussi,



    Thanks for your feedback!



    Unfortunately that operation failed with a TestComplete MSSCCI error.



    I then tried to add and existing project to the test suite but it failed with the same MSSCCI error.


    Can you post an image that will demonstrate the error message?



    Thanks in advance.
  • Dmitry_Nikolaev's avatar
    Dmitry_Nikolaev
    Staff
    13 years ago

    Hi Jussi,



    So, could you please send an image or the text of the error you get? Unfortunately, it is not clear what exactly error you get from your description.