| || |
Configuration Control of Test Scripts Using VSS
Our company started using Visual Source Safe. This tool is also new for me.
So, now we are trying develop Automation section tree structure that consist of two Parts
1. Automated Test Development (ATD) – Developers’ responsibility
iii. Functional Scripts
b. Project name
i. Test Case development Structure
i. Use files – file that include few other use files
d. Object files -- .obj files
e. Source code
i. Window declaration Files.inc
ii. Function definition Files.inc
b. Object files
2. Test Execution – for testers who use developed Automated scripts for testing. The Batch file is written to pull latest version of shared files ŕ CM manager’s idea
a. Project name
i. Test Data
ii. Log File
iii. Environment (necessary application should be open)
iv. Script and Object file to lunch script
v. Object file
Is any one can give me other idea about this VSS Automation structure. Any inputs would be very appreciated.
Re: Configuration Control of Test Scripts Using VSS
VSS has 3 ways to utilize it:
1) Manually, via the Windows GUI
2) Manually or Batch, via the command line interface.
3) Programatically, via the COM interface.
You can generally automate most of the features using the commandline interface and ugly batch files. If this is not adequate and you really need to unharness the automated facilities, then use scripting or code to drive the exposed COM interface. The interface exposes full functionality to the VSS engine and is flexible enough that one could effectively rewrite the standard VSS GUI and provide an alternative interface (even an HTML interface if you were willing to put in the effort).
Bugtoaster - A global community eradicating the world of computer crashes.
John Schacher Bugtoaster
- Like SETI, but think computer crash research!