| || |
\"Version Control\" and \"Baseline\"
I have done some study on features provided by baselines and version control in QC 10 premier edition. On the face of it, there seems to be nothing which I cannot do in Version Control which I can do through baselines.
Some obvious restrictions are that versioning locks everything during check out, a check out would have to made just for storing a version and also it would have to be done for each of the requirements/test cases separately.
I know this already is enough reason to continue having baselines in the mix too, but is there any other USP of baselines over version control.
Re: \"Version Control\" and \"Baseline\"
It is not a matter of choosing one over the other, the baseline functionality sits over the top of version control. A baseline is a snap-shot in time of a collection of related entities and each entity is identified by its version number at the time the baseline was created.