Forum Discussion

vthomeschoolmom's avatar
vthomeschoolmom
Super Contributor
14 years ago

visual source safe

I am trying to understand TC integration with Visual Source Safe. I have a few questions.



1. I have all my projects already IN VSS. How to I link the project in VSS to the open project in Test Complete.



2. Is there a list of all files that are part of a project by extension and what they do? I want to NOT source safe the BAKs for instance and the log files. Someone on my team mentioned that there are files saved as part of user specific workspace layout choices that are saved with the project.  A comprehensive list of all files that might be part of a project would help me with developing our source control procedures.



Are there any white papers or whatever available on source control integration that I have been unsuccessful at finding? Thanks.






9 Replies

Sort By
  • vthomeschoolmom's avatar
    vthomeschoolmom
    Super Contributor
    14 years ago
    Also test Complete seems to want the script files as binary. I can open them in notepad. But if I attempt to change the type in Source Safe to text, the files get corrupted and unhappy.



    This renders the Source Safe show differences non-functional. Is there a work around for that?
  • AlexKaras's avatar
    AlexKaras
    Icon for Champion Level 2 rankChampion Level 2
    14 years ago
    Hi Lane,



    > How to I link the project in VSS to the open project in Test Complete.

    I hope that http://smartbear.com/support/viewarticle/11011/ and http://smartbear.com/support/viewarticle/12215/ might provide you with the relevant information.



    > Is there a list of all files that are part of a project by extension
    and what they do?

    http://smartbear.com/support/viewarticle/12217/




    > Also test Complete seems to want the script files as binary. [...]

    TestComplete files can be in Unicode format. AFAIR only VSS6.0d can work with unicode files. Otherwise, the only option is store files as binary and use some third-party tool (e.g. BeyondCompare by Scooter Software) to see file differences.
  • vthomeschoolmom's avatar
    vthomeschoolmom
    Super Contributor
    14 years ago
    http://smartbear.com/support/viewarticle/12217/



    This is very helpful. Thank you. One question I have is is there information about what triggers an update to the project suite and project files?



    The requirement we seek to understand is for any given change we wish to make to a script within a project, what is the minimum file(s) that we can check out and check back in? So I would need to know what types of changes will cause a change to the









    • .pjs - The project suite file.


    • .mds - The project file.




    Files.



    Thanks!
  • vthomeschoolmom's avatar
    vthomeschoolmom
    Super Contributor
    14 years ago
    Could you identify what personal settings are stored in *.pjs.tcls and *.mds.tcls?



    Thanks


  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    As far as I know, there are the "Local Values" of project and project suite variables that are stored in those files.  That's the primary use of those files as I know it.  For the MDS file, there's the path location for any TestedApps that may be configured (since that may change from machine to machine) and the pathing to the log file for the local machine (again, something that may be machine specific).



    For the PJS file, it primarily contains the locations of the tcLS files for the projects that are contained within the project suite and, again, the location of the log file for the project suite.



    Note that, since these items are machine specific by definition, this is why they are typically not included in a source control system.
  • AlexanderM's avatar
    AlexanderM
    Icon for Staff rankStaff
    14 years ago

    Robert, thanks for sharing this information.





    Lane, please note that the contents of the files is not documented, so it may change in the future. Please be careful if you are going to rely on the files' contents.