CodingForums.com - View Single Post

Old Pedant · 01-11-2013, 08:29 PM

I say again: Unless you will pass *DIFFERENT* parameters to TestExecute each time, you do *NOT* need JavaScript to get involved.

You *CAN* just specify the command line arguments via the Task Scheduler. Did you not know that?

And even if you couldn't, you could instead create a ".bat" file that contained something like

Code:

    TestExecute  zambonis 337 Z$4

and then schedule the ".bat" file.

You need to explain why you think you need JS to get involved here.

01-11-2013, 08:29 PM	PM User \| #5
Old Pedant Supreme Master coder! Join Date: Feb 2009 Posts: 23,200 Thanks: 59 Thanked 3,996 Times in 3,965 Posts	I say again: Unless you will pass DIFFERENT parameters to TestExecute each time, you do NOT need JavaScript to get involved. You CAN just specify the command line arguments via the Task Scheduler. Did you not know that? And even if you couldn't, you could instead create a ".bat" file that contained something like Code: TestExecute zambonis 337 Z$4 and then schedule the ".bat" file. You need to explain why you think you need JS to get involved here. __________________ An optimist sees the glass as half full. A pessimist sees the glass as half empty. A realist drinks it no matter how much there is.