| || |
QuickTest source code control
I have a large QTP script containing a dozen or so "actions", all of which need to be in a source code control system; there are several people all attempting to work on the scripts at the same time. Unlike working with, say, C++, I find that the script source code is not flat text; it contains generated XML embedded where I use variables and parameters. Has anyone had any experiences, good or bad, keeping such scripts/actions in ClearCase or similar? I would like to use the sophisticated branching & merging features but I am nervous because the generated XML code is out of my control. Any thoughts greatly appreciated.
Re: QuickTest source code control
You need to keep the tests folder and contents.
We are implimenting CVS which has been used for QTP sucessfully.