OT - RE: VSS and Robot 2002
User Tim Gerrells (firstname.lastname@example.org) posted:
MArk, I'm just coming up to speed on the 2002/datastore motif, so don't know
the file structure you're describing for script/VPs/whatnot. Am still
repo-bound. If you want, offline tip me off on details of what you're doing.
As SCM Mgr also, I have a number of batch and script files that interact
with VSS 6 on the command line level and via ActiveX API level. For simple
check out and check in, there's probably a fairly straightforward way to
Re: OT - RE: VSS and Robot 2002
User MArk B. (email@example.com) posted:
Because it's you asking Tim. :-)
Here's the quick version.
Assuming you already have the scripts in the project.
Overview of the steps are:
Create a test plan
Create a test case folder
Create a test case
Associate the script to the test case
Export the test case and script into a package
More Detailed version:
(Select and right click to do just about everything)
In the "Planning" tab of the main browser you create a test plan
Open the test plan
Insert a Test Case folder.
Under the Test Case folder insert a Test Case (A test case is the main
object in the new TM.)
Name the test case. (You might use the same name as the script you will be
associating to it)
Click the 'Implementation' tab
For the Automated implementation section click the select button, pick GUI
- On the Select Test Script dialog select the test script (Seems a strange
thing to do here doesn't it.)
Close the test case dialog
Now do the export:
Right click the test case and select export
Uncheck everything except "Associated Implementations"
Set the path and name of the parcel file
When importing, you pick the package file and then the stuff that's in it
you want to import. I can't remember what all that amounts too or the level
of detail you can filter too. You might have to import the entire TC or you
might get away with just the scripts.
You'll handle SQABasic files outside of TM.
I ain't doing this. I am suggesting that this might be a work around for
the unviable "zipping up the whole damn project" alternative. (Among other
things, without being able to rename scripts, or damn near anything else for
that matter, I'm not going to convert to the new version.)
In addition to the manual method described above there might be a way to use
the TM api to initiate the export to create the test asset parcel file.
Either way I think you'll have to do the associating of the script with the
TC manually. I'm not sure of that but I don't recall seeing any reference
to being able to do that kind of thing via the API.
One point. It sounds like a bunch of work but it really isn't that much
once it gets setup.
Things to watch for. Test Scripts can be associated to multiple test cases.
There are no restrictions. You might export these two test cases with the
same script but different version of it and then go about importing the test
case later. Who knows what might happen. A way to make this safe might be
to create a Test Plan with a set of test cases in it that is explicitly for
handling version control. Have a one to one ratio of test scripts to the
test cases. All this begs the question, WHY THE HELL IS CONFIGURATION
MANAGEMENT SO DAMN HARD TO DO! (please excuse me)
"Tim Gerrells" <firstname.lastname@example.org> wrote in message