Execution via Scheduled Task: Arguments ignored

[bennylew]

Hi people,

I work with Ranorex 5.2.1 on Windows 7 64bit.

I want to set up virtual machines and plan and trigger our Tests with scheduled tasks. This works fine, except for the arguments.

Action setup for scheduled task
Program/Script: "C:\Program Files (x86)\Ranorex 5.2\Workspace\Google\Google\bin\Debug\Google.exe"
Arguments: /rf:report.rxlog

This setu is only an example, my test opens IE, calls google.com and checks if the search button exists. The report name is also just temporarily.

When I run this scheduled task, the execution works, but no report is generated. For debugging I tried to execute the following command on cmd:
"C:\Program Files (x86)\Ranorex 5.2\Workspace\Google\Google\bin\Debug\Google.exe /rf:report.rxlog"

This works fine on cmd, but not on scheduled task. Does anybody have the same problem and know hot to solve it?

[odklizec]

Hi,

I guess the problem is that the report argument has not specified path and therefore points to "program files"? And if the scheduled task is not started in admin priviledges, it cannot write to "program files". So you either need to specify a report path outside the "program files" or you need to instruct the task scheduler to run your job with admin priviledges. It should be possible by enabling "Run with highest privileges" task scheduler option.

[krstcs]

I would recommend that you try using Jenkins instead of task scheduler. It is much more useful in these types of situations because it can run any batch script that you tell it. I find it much easier to manage than using each individual machine's task scheduler since you can manage multiple systems from one central server.

[bennylew]

Thanks for your replies.

@odklizec: Unfortunately this hints doesn't solve my problem.
@krstcs: I already read about Jenkins. For the CI we actually want to use TFS, so is it possible to run TFS and Jenkins in parallel mode (TFS for building and Jenkins for plan and execute the testsuites?)

[krstcs]

I don't use TFS, so I couldn't tell you for sure about it, but I don't see why you couldn't. Jenkins doesn't care and I doubt TFS will either.

[bennylew]

I solved the initial problem by specifying not the "arguments", but the "start in" parameter für the schedule task. Now the report will be saved in this location.