If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Watch folder suite.

Before I start writing this from scratch,

Is there anyone here who has created a script ( or something else) that will constantly keep running scripts that are in a folder non-stop. Basically the goal is to be able to start a testscript that will launch script after script in a specified folder, and if new scripts are dropped in the folder, they will eventually make it through the cycle?

Re: Watch folder suite.

Not yet done. But should be a 10 minutes job using Excel Macro or even silktest. Create a suite file for all the .t files in a specified folder. Then you just need to invoke partner.exe from command line to run the .s file.

Re: Watch folder suite.

I plan on using SilkTest, and I was thinking of writing a *.t script which will just launch a *.t from a folder. The problem that i may run into is invoking a script from a script, Not to sure if this can be done, or if it will cause a problems? When I get the desgin all done i will post what i have.

Re: Watch folder suite.

Ok, I have the whole system in place and i can drop a test into a folder and it will get process into the cycle. Only one problem, I still am having a difficult time to launch the testcase from a testcase.

Re: Watch folder suite.

I have never used a mutlitestase. Also it' not actually calling a testcase, ( I was not very clear about that, sorry) what I have set up right now is a routine, written in a main function which is trying to execute another instantance of silktest to run the testscript.t file. and when the file silk loads up, it just sit's there, and reports that is waiting the the local agent, and the agent is already loaded up. Hope that is a little bit more clear as to what i am trying to do. Maybe you have a better way or a suggetion.

Re: Watch folder suite.

I think the problem might be arising because you are using one instance of SilkTest to start another. So when the second one starts it sees that the local agent is busy with the first instance. But of course the first instance is waiting for the second instance to finish so you are at a deadlock.

I think you would probably be better off writing the control script in another language and avoiding the conflicts between multiple instances of SilkTest.