I looked through the board for 'scheduling SilkTest scripts' and saw numerous means of scheduling tests (DOS, cron, Windows Scheduler). I just wanted to ask the population what they found worked the best for them?
I'm not partial to any of the methods and I'm curious to hear any negative/positive sides. Any help would be greatly appreciated.
The methods that you have listed above are essentially the same. The only draw back that I see in all those methods is once script finishes what it was doing, SilkTest will still be up and running and you would have to kill it via script, by hand or by some other means (I could be wrong on this though).
Once I've see a scheduler written in the SilkTest itself. Person, who implemented this, basically was stuck in the endless loop until a certain time and once that time came, he broke out of a loop. That is definitely a possibility, but it's a waste of a very expensive resource!
If the scheduling program that you use starts SilkTest via the command line you can use the -q command line argument and SilkTest will close after finishing the script/testplan that you specify.
For example, "partner.exe -q c:\tests\mytest.pln" would start SilkTest, run mytest.pln and then exit. The good thing is that SilkTest remembers which files were open so you can simply re-open SilkTest to see the results.
check out SilkTest help files for the command line options and switches. To execute a command on a remote machine via a DOS box, look into sysinternal.com psexec. it's a little tool that does just that [img]/images/graemlins/wink.gif[/img]