Topic: Query in WINRUNNER

Also, telling us that you have called a script with certain variables as a parameter doesn't tell us anything about how the script works. Without the code from the script you might as well have not posted as there isn't any way for any of us to assist you, even if we were inclined.

Again, telling us you received "Not Completed" for your batch runs doesn't inform us well enough on what the issue might be. Where are you calling these tests from? Are they from the command line/Test Director, or from a list of called scripts in a driver script? Not telling us the error the report is stating won't get you any closer to what you need to do as well.

As a final comment, the tutorial you are stepping though is there for you to take the time and research the information on the tool that is contained in the Tutorial, Users Guide, TSL Guide and on line at Mercury's Support site to make sure you are able to work through the issues you may encounter while using the tool. Take the time and try to research what you are missing in relation to the errors you are receiving.

Contrary to what most people believe it isn't going to be easy, or simply clicking the record button, doing some stuff and be done. You are going to constantly run into situations like this one and this is just the first step to overcoming them.