I have a SYS_EXE for a batch file i normally run with SILK .It was working good till i got a specific set of data i tried working with.
Whenever i run my testcase for that data .Silk will run the batch file.The batch file will run what it is supposed to thru the commandline option.I see the new process i want to run thru the batch file come up in task manager.But Silk will not complete the process.
I do the same thing manually the batch file runs fine.
Assuming you're using SYS_Execute() to execute your batch file, the following is straight out of the help on SYS_Execute():
Do not use SYS_Execute to execute .reg files; use the Start command instead. SYS_Execute was designed to execute commands that do not require user input and that terminate almost immediately after it has been executed. SilkTest waits for any command that brings up a process requiring user input. For example: SYS_Execute ("freecell.exe") starts Freecell in an invisible window and SilkTest does not continue until the Freecell process is terminated. On the other hand, SYS_Execute("start freecell.exe") starts Freecell in a visible window, and still SilkTest does not continue until the Freecell process is terminated.
<font size="2" face="Verdana, Arial, Helvetica">
Have you ever noticed? Anybody going slower than you is an idiot, and anyone going faster than you is a maniac.
My batch file runs a small exe which will unzip data and rebuild the tables in an internal database with the new data.
Manually if u r in the right directory, the commandline usage will start and complete the process and it does not require any user input once executed.
For this new set of data it just takes a longer time to complete about 2/3 minutes.
Silk runs the same batch file, it gets into the right directory starts the process i can see in the task manager that silk has started the process it is supposed to. I wait for 25 minutes the process is not finished and silk is still waiting on the process to complete.
I am not sure what the problem is because that damned batch file runs perfectly if i run it manually.
Are you passing arguments to the batch file? We use batch files and VB Scripts along with our tests and have found when we pass in arguments that have spaces (like the path c:\Progrm Files) we get strange results.