Hi there,
I am using Ranorex 8.2 option to run multiple suites at once (that used to be serveral projects before).
To define wich testcases has to be executed I use a global parameter "testset" by wich the testcases are checked/unchecked.
The testrun starts via batch "tests.exe /gp:testset='All'"
Unfortunately the command line parameter does not update the global parameter anymore.
Do I miss something for the new Version
command line parameters and 8.2
command line parameters and 8.2
K
-----------------------
Ranorex 9.3
Ranorex Certified Professional (01/2017)
ISTQB Certified Tester Foundation Level (07/2018)
-----------------------
Ranorex 9.3
Ranorex Certified Professional (01/2017)
ISTQB Certified Tester Foundation Level (07/2018)
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: command line parameters and 8.2
Hi kathrin,
Thank you for reaching out to us in regards to your command line parameters question as I would be happy to help.
Please give the below a try and let me know if you continue having any issues:
There is a quick reference that can be found within our user guide here:
https://www.ranorex.com/help/latest/ran ... earguments
I hope this helps and I look forward to hearing from you!
Regards,
Jon
Thank you for reaching out to us in regards to your command line parameters question as I would be happy to help.
Please give the below a try and let me know if you continue having any issues:
Code: Select all
Syntax:
/param|pa:[global parameter name]=[value]
tests.exe /pa:testset=All
and if you need to specify the test suite:
tests.exe /ts:<Path_to_test_suite>.rxtst /pa:testset=All
Example: test.exe /ts:MyTestSuite2.rxtst /pa:testset=All
I did not need to specify a path since MyTestSuite2.rxtst resides in the dame directory
https://www.ranorex.com/help/latest/ran ... earguments
I hope this helps and I look forward to hearing from you!
Regards,
Jon
Re: command line parameters and 8.2
Hi Jon,
thank you the solution works
But why did you change that anyway?
Now i have to change every call (ci/cd ect.) of "tests.exe" and that kind of sucks
thank you the solution works
But why did you change that anyway?
Now i have to change every call (ci/cd ect.) of "tests.exe" and that kind of sucks
K
-----------------------
Ranorex 9.3
Ranorex Certified Professional (01/2017)
ISTQB Certified Tester Foundation Level (07/2018)
-----------------------
Ranorex 9.3
Ranorex Certified Professional (01/2017)
ISTQB Certified Tester Foundation Level (07/2018)
Re: command line parameters and 8.2
Hi again,
I now ran into an corresponding problem.
When I try to start a testset with blanks the parameter gets cut like
/pa:testset=MUST HAVE -> MUST
/pa:testset='MUST HAVE' -> 'MUST
How do I fix that?
I now ran into an corresponding problem.
When I try to start a testset with blanks the parameter gets cut like
/pa:testset=MUST HAVE -> MUST
/pa:testset='MUST HAVE' -> 'MUST
How do I fix that?
K
-----------------------
Ranorex 9.3
Ranorex Certified Professional (01/2017)
ISTQB Certified Tester Foundation Level (07/2018)
-----------------------
Ranorex 9.3
Ranorex Certified Professional (01/2017)
ISTQB Certified Tester Foundation Level (07/2018)
Re: command line parameters and 8.2
I normally put full double quotes rather than single quotes around my command-line parameters:
Code: Select all
/pa:testset="MUST HAVE"
Re: command line parameters and 8.2
I just checked the code base, because I cannot remember that we ever had a "gp" argument
As far as I can tell from the code, we did not change the command line arguments for setting parameters.
From which version did you upgrade from?
Regards,
Alex
Ranorex Team