I have this question on running the scripts if anyone can explain the entire process. I mean I have a set of scripts and the database to run against then how would you set up the entire process. For eg I have a set of scripts for a specific dataset for a specific build, how would you cover up the entire process so that in the future if you have multiple set of scripts with multiple datasets for different builds, what kind of directory structure you need, how can you cover the process, do I need naming conventions, what kind of files go in this process I don't know. Can anyone elaborate on this please.
Wow, that's a really big question with an even bigger answer. The kind of answer you are looking for would be pretty much an entire chapter or two in a book on QA Automation.
But really, why would you have multiple sets of scripts? The advantage of automation frameworks is that you can write one suite of automation scripts that are robust and reusable - if you're not doing this then you're not getting a good return on your time invested in generating the scripts.
So, write one set of scripts. Create a variable at the beginning that establishes which dataset you are using, and edit just that variable as needed for different test runs. Sure, maybe you'll have to build a few If..Then statements here and there in your scripts to handle different conditions that arise because of the varying data, but it's much much easier to create and maintain the scripts this way.
The same holds true for builds. If you can't simply focus on the latest, greatest build but must actually maintain automation across multiple different builds, then I recommend still using just one set of automation scripts. Stick the build number into a QTP Environment Variable and rely on If..Then statements to examine that build number and handle differences that might arise because of it.
I think setting it up that way will solve most of your problems and eliminate some of your questions right from the start.
Sorry for the late follow up I was on vacation. My AUT is a COTS product and the functionality can be changed as per client needs so there is a possibility of multiple set of scripts. We have the framework Sai which is based on QC directory structure.