If you want to do it from the command line, that will work. Note that you can pass in "-r" parameter a testplan, or a script file, or a test suite, etc.
You can also set the project (.vpt) in the command line:
partner.exe -q -proj <path to project>.vtp -r <path to script>.t arg1 arg2 ... argn
and one of the arguments could be the test case within that script to be executed, for instance.
From within the main() function you can access the list of arguments by calling the function GetArgs():
LIST OF STRING lsArgs
lsArgs = GetArgs ()
so that you can pass a variable number of arguments without having to declare them in the main function header.
Ahhh, I don't use the command-line too much, so I didn't know you could use it to pass in your parms. I was just assuming based on your question that you had tried the command-line and it didn't work for you.
So use the command-line if that's convienient for you. Or like I mentioned, you can pass in parms to the main from a testplan. Choose whichever way works best for you. It's great that Silk gives you the flexibility to do either.
Thanks a lot for your replies! GetArgs is amazing [img]/images/graemlins/wink.gif[/img]
Brian, what I'm doing right now is "automating SilkTest". I know it sound's ridiculously funny, but I have to run my scripts daily. Since the project that I'm working on is still young, my scripts run only for about an hour (at most). That means that I'm waisting an hour of my time just by looking at the screen and telling myself that I could be doing something else on my computer right now.
So, to resolve that, I'm using a windows scheduler to automatically start silktest.
The passing in command line arguments comes into play when I do script debugging. The command line that I'm specifying will test my script whether to install latest build of AUT or not. Installation takes about 5-7 mins.
Another reason is very simple, I want to learn something new and if I find it beneficial for my purposes, start using it [img]/images/graemlins/smile.gif[/img]