I currently have a set of QA Run scripts which are used for baseline regression testing on all new software releases.
A current gap i have, is that for any changes made to the scripts, there is no on-going change control process whereby the user who is amending the script, can fill in a template/form giving all details of the amendment.
The amendment may be to incoroporate changes to the software functionality, apply standards etc,etc.
The revision history QA_Guy suggested is a traditional method. There is also the history of changes for each script in your db...my only quibble with that is you can't add a description of each change.
So, you have to OPEN a version to read teh history to find out if its the item you are after.
These two inputs seem to be the most efficient way to track changes at the moment ( unless you use a version control tool like MKS Source Integrity or Visual SS ).
Man, it would be nice to be able to code QARun and store scripts in VSS. I guess you could do it and paste it back into QARun...lol...to time consumming. Heck, it would be great just to use a better editor...atleast one that doesn't crash all the time.
"If your not part of the solution, there's good money to be made in prolonging the problem."
One thing that we did was to check the database into our source code change migration system. This allowed testers and developers access to the most recent qarun database and allowed the process for code reviews with appropriate comments to be used.