Has anyone had success using VSS or some other CM tool to manage source control for QTP scripts (or WinRunner Scripts). When you create a script, there are many files and folders that get produced with it. So, is it necessary to check in everything? Also, we seem to run into disk space issues trying to use the VSS addin for Quality Center.
Sometimes we check in our scripts to TestDirector, but it doesn't seem to do a good job of versioning. What are some of the tools and processes everyone uses for this?
We looked into this in some depth as I wanted to version control our QTP scripts within PVCS Dimensions. Because there are so many dependencies between modules we found it was getting too complicated and the potential for error was too great. The only, very unsatisfactory, solution we came up with was to zip up the modules and version control those. So we ditched the whole idea and now control the scripts within QTP itself.
Originally posted by peternairn: So we ditched the whole idea and now control the scripts within QTP itself.
<font size="2" face="Verdana, Arial, Helvetica">Peter, could you expand on that? If you see one of my recent posts on the QTP forum you will see I'm seeking a similar solution. I'd appreciate your response on this.
I have not tried this due to limitations from HPQC administrators!!
I was once going through the HPQC documentation and noticed that we can perform QTP version control in HPQC.
I am not sure how it works, I have never been able to work on it.. Maybe one day, I can develop a business case and present it to the management.
The Version control add in was provided in the Add in page of HPQC.
Maybe, you would like to try using HPQC for version controlling your QTP scripts.