It seems like Ranorex doesn't use any of the command line arguments defined in the "Project options" "Debug" tab in Studio when executing tests remotely. At least, that's what I experience when trying to assign a value to a variable using command line arguments.
Isn't that a bug? Or is there a natural reason for it?
Has anyone somehow been able to overcome that limitation?
Best Regards
Bo
Remote execution with command line parameters
Remote execution with command line parameters
Best Regards
Bo
Bo
Re: Remote execution with command line parameters
Hi,
I'm not using Ranorex remote execution, but I know that Debug >> command line arguments definitely works, if the test is running locally. Are you sure the test was in "debug" mode, while running remotely?
I'm not using Ranorex remote execution, but I know that Debug >> command line arguments definitely works, if the test is running locally. Are you sure the test was in "debug" mode, while running remotely?
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Remote execution with command line parameters
I am in the same boat as boegvald. I am running Studio 10.5.0 and I have the command line argument set in the debug properties. When I execute the tests locally, the global parameters get set correctly, but when I execute the tests on a remote system using the agent, the command line arguments set in debug DO NOT get passed along. The command that gets executed is "REMOTEVM.exe" /zr /ts:"REMOTEVM.rxtst" /rc:"TestRun"
There should be a way to modify the agent command line parameters.
There should be a way to modify the agent command line parameters.
