Re: How to creat a datastore like CVS to controll the ROBOT script check in / check out
I don't know what tool is "best" for version control, but CVS will do as well (or as bad) as any.
More importantly, there is no tool that is smart enough to know what to check in/check out automatically.
Even Rational ClearCase does not do this in a granular way (ClearCase support will tell you to check in the whole datastore)
The reason that it is non trivial is that a single Robot script can create and depend on a lot of files. In particular, each time you do a VP, a new baseline file is created, which you need to remember to add to source control, and then check out every time you work on the script.
For scripts, I recommend to follow ClearCase advice (even if you use CVS, sourcesafe, or whatever): not keep scripts checked out while you work on them.
When ready, do a rapid check in + check out of the whole datastore, and resolve any differences that another tester might have made, by hand.
In practice, I find that it is rare to get 2 testers working on the same script in parallel.
It does, however, happen more often if you use SQABasic libraries a lot.
So what I do is have the custom SQABasic libraries kept outside of the testdatastore (you can change the path in Robot Tools>General options>preferences). I do not have any actual test scripts in libraries (and more importantly no verification points). For scripts that you want to able to reuse a lot, make them small and modular by treating them as scritps and making use of the CallScript function a lot.