Hello,
Variables in the commandline argument reportfile will not be resolved in Ranorex 4.0.1.
example: %S_%Y%M%D_%T.rxlog
Best Regards
Andreas
variables in commandline argument reportfile not resolved
-
- Posts: 36
- Joined: Mon Sep 20, 2010 10:59 am
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: variables in commandline argument reportfile not resolved
Hello Andreas,
I checked the argument and in my case it worked as expected, could you please check if the following command works on your machine: "C:\...\bin\Debug>YourExe.exe /rf:C:\Test\%S_%Y_%T.rxlog"?
Could you please also test it with the new Ranorex version, here is the link: Ranorex 4.0.2 and please use the setup.exe for the installation.
Thanks,
Markus
I checked the argument and in my case it worked as expected, could you please check if the following command works on your machine: "C:\...\bin\Debug>YourExe.exe /rf:C:\Test\%S_%Y_%T.rxlog"?
Could you please also test it with the new Ranorex version, here is the link: Ranorex 4.0.2 and please use the setup.exe for the installation.
Thanks,
Markus
-
- Posts: 36
- Joined: Mon Sep 20, 2010 10:59 am
Re: variables in commandline argument reportfile not resolved
Hello,
Seems to be a fixed bug of 4.0.1. It works with 4.0.2.
Best Regards
Andreas
Seems to be a fixed bug of 4.0.1. It works with 4.0.2.
Best Regards
Andreas
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: variables in commandline argument reportfile not resolved
Hello,
You are welcome
Regards,
Markus (T)
You are welcome
Regards,
Markus (T)
Re: variables in commandline argument reportfile not resolved
Hi,
I'm sorry to reopen this old post but it seems the same problem is still reproducible with compressed reports. Using below command line results with unresolved variables in output report file name:
/zr /zrf:c:\temp\%S_%Y%M%D_%T.rxzlog ends with %S_%Y%M%D_%T.rxzlog report name. Reproducible with Ranorex 5.0.2.
I'm sorry to reopen this old post but it seems the same problem is still reproducible with compressed reports. Using below command line results with unresolved variables in output report file name:
/zr /zrf:c:\temp\%S_%Y%M%D_%T.rxzlog ends with %S_%Y%M%D_%T.rxzlog report name. Reproducible with Ranorex 5.0.2.
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
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: variables in commandline argument reportfile not resolved
Hello odklizec,
Thank you for reporting this issue. I have already added the issue to our internal bug-tracking system. We apologize for any inconvenience this may cause.
Regards,
Robert
Thank you for reporting this issue. I have already added the issue to our internal bug-tracking system. We apologize for any inconvenience this may cause.
Regards,
Robert
Re: variables in commandline argument reportfile not resolved
Hi,
Sorry for reopening this post one more time, but I guess the issue is not fixed yet? Or maybe it's broken again?
After an attempt to use the below command line...
the output report file name looks like this:
It seems the same now happens both with compressed and uncompressed report.
Reproducible with Ranorex 5.3.2.
Sorry for reopening this post one more time, but I guess the issue is not fixed yet? Or maybe it's broken again?
After an attempt to use the below command line...
Code: Select all
C:\test\bin\test.exe /zr /zrf:C:\test\reports\%S_%Y%M%D_%T.rxzlog
Code: Select all
YD_T.rxzlog
Reproducible with Ranorex 5.3.2.
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
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: variables in commandline argument reportfile not resolved
Hi odklizec,
Unfortunately, we are not able to reproduce the issue with Ranorex 5.3.2. The fix for this issue was included in Ranorex 5.2.X. May I ask you to provide further details?
Robert
Unfortunately, we are not able to reproduce the issue with Ranorex 5.3.2. The fix for this issue was included in Ranorex 5.2.X. May I ask you to provide further details?
- • operating system
• Did you start the console with admin privileges?
Robert
Re: variables in commandline argument reportfile not resolved
Hi Robert,
OK, I found 100% reproducible steps (reproduced with Win7 Pro and Win Server 2012 R2). It seems it happens only if the command line is started from batch file!
Just add the command line to *.bat or *.cmd file. I found no way to start the bat/cmd file with admin privileges, but it's possible to do so via new shortcut created for such bat/cmd. However, this did not help either.
OK, I found 100% reproducible steps (reproduced with Win7 Pro and Win Server 2012 R2). It seems it happens only if the command line is started from batch file!
Just add the command line to *.bat or *.cmd file. I found no way to start the bat/cmd file with admin privileges, but it's possible to do so via new shortcut created for such bat/cmd. However, this did not help either.
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
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: variables in commandline argument reportfile not resolved
Hi odklizec,
Please ensure that you are escaping the '%' sign within your bat file.
E.g.:
Regards,
Robert
Please ensure that you are escaping the '%' sign within your bat file.
E.g.:
Code: Select all
..\test.exe /zr/zrf:..\%%S_%%Y%%M%%D_%%T.rxzlog
Regards,
Robert
Re: variables in commandline argument reportfile not resolved
Ah, silly me Sorry for false alarm! I'm always forgetting about escaping in batch files.
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
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: variables in commandline argument reportfile not resolved
Hello odklizec,
No problem, you're welcome.
Regards,
Robert
No problem, you're welcome.
Regards,
Robert